StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.4, the REST API getUsers endpoint in StudioCMS uses the attacker-controlled rank query parameter to decide whether owner accounts should be filtered from the result set. As a result, an admin token can request rank=owner and receive owner account records, including IDs, usernames, display names, and email addresses, even though the adjacent getUser endpoint correctly blocks admins from viewing owner users. This is an authorization inconsistency inside the same user-management surface. Version 0.4.4 fixes the issue.
CVE-2026-32638
LOWPre-NVD 2.72.7
EchelonGraph scoreLOW confidence
This low-severity CVE scores 2.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
2.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.7Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 2.7
- EG Score
- 2.7(low)
- EG Risk
- 17(Track)EG Risk 17/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity27% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
March 18, 2026
Last Modified
June 17, 2026
References (3)
- security-advisories@githubhttps://github.com/withstudiocms/studiocms/commit/aebe8bcb3618bb07c6753e3f5c982c1fe6adea64
- security-advisories@githubhttps://github.com/withstudiocms/studiocms/releases/tag/[email protected]
- security-advisories@githubhttps://github.com/withstudiocms/studiocms/security/advisories/GHSA-xvf4-ch4q-2m24
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 14:41 UTCEG score recompute
- 2026-07-27 14:27 UTCOSV refresh
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS p94CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS p94CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS p97CRITICAL
- CVE-2019-13360EG 9.8EPSS p98CRITICAL
- CVE-2019-12866EG 9.8CRITICAL
- CVE-2019-9756EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-32638?
CVE-2026-32638 is a low vulnerability published on March 18, 2026. StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.4, the REST API getUsers endpoint in StudioCMS uses the attacker-controlled rank query parameter to decide whether owner accounts should be filtered from the result set. As a result, an admin token…
When was CVE-2026-32638 disclosed?
CVE-2026-32638 was first published in the National Vulnerability Database on March 18, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32638 actively exploited?
CVE-2026-32638 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.9% of all scored CVEs.
What is the CVSS score of CVE-2026-32638?
CVE-2026-32638 has a CVSS v3 base score of 2.7 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-32638?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32638, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-32638
Is Your Infrastructure Affected by CVE-2026-32638?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.