Back to CVE records
Low 2.7Published Mar 18, 2026

CVE-2026-32638StudioCMS REST getUsers Exposes Owner Account Records to Admin Tokens

Updated under an hour ago ()

Does this affect you?

It affects withstudiocms studiocms and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
2.7 LOW (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
Weakness (CWE)
CWE-639
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
GitHub_M
NVD analysis
Analyzed
Record last updated
Mar 19, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
withstudiocms studiocms
withstudiocms:studiocms (from the name)
before 0.4.4
CNA record
studiocms studiocms
studiocms:studiocms
before 0.4.4
NVD

References

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.