CVE-2026-32638 StudioCMS REST getUsers Exposes Owner Account Records to Admin Tokens
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- Proof of concept public · automatable: no · technical impact: partial
Description
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.
Upgrade path
3 packages: 2 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| @studiocms studiocms | < 0.4.4 | 0.4.4 | Fixed |
| npm studiocms(npm) | < 0.4.4; <= 0.4.3 | 0.4.4 | Fixed |
| withstudiocms studiocms | = < 0.4.4 | No fix listed | Versions listed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| withstudiocms studiocms | = < 0.4.4 | No fix listed |
| npm studiocms(npm) | <= 0.4.3 | No fix listed |
| @studiocms studiocms | < 0.4.4 | 0.4.4 |
| npm studiocms(npm) | < 0.4.4 | 0.4.4 |
References
- https://github.com/withstudiocms/studiocms/security/advisories/GHSA-xvf4-ch4q-2m24 exploit mitigation vendor-advisory
- https://github.com/withstudiocms/studiocms/commit/aebe8bcb3618bb07c6753e3f5c982c1fe6adea64 patch
- https://github.com/withstudiocms/studiocms/releases/tag/studiocms@0.4.4 product release-notes
- nvd.nist.gov third-party-advisory vendor-advisory
- github.com
- github.com product