Vulnerability 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.
CVSS Score
LOW
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Studiocms | Studiocms | < 0.4.4 |
Related Weaknesses (CWE)
References
- https://github.com/withstudiocms/studiocms/commit/aebe8bcb3618bb07c6753e3f5c982cPatch
- https://github.com/withstudiocms/studiocms/releases/tag/[email protected]ProductRelease Notes
- https://github.com/withstudiocms/studiocms/security/advisories/GHSA-xvf4-ch4q-2mExploitMitigationVendor Advisory
FAQ
What is CVE-2026-32638?
CVE-2026-32638 is a vulnerability with a CVSS score of 2.7 (LOW). 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...
How severe is CVE-2026-32638?
CVE-2026-32638 has been rated LOW with a CVSS base score of 2.7/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-32638?
Check the references section above for vendor advisories and patch information. Affected products include: Studiocms Studiocms.