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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| withstudiocms | studiocms | < 0.4.4 |
References
- https://github.com/withstudiocms/studiocms/commit/aebe8bcb3618bb07c6753e3f5c982c1fe6adea64Patch
- https://github.com/withstudiocms/studiocms/releases/tag/studiocms@0.4.4Product, Release Notes
- https://github.com/withstudiocms/studiocms/security/advisories/GHSA-xvf4-ch4q-2m24Exploit, Mitigation, Vendor Advisory
Timeline
- Published
- Mar 18, 2026
- Last modified
- Jun 17, 2026
- NVD status
- Analyzed