CVE-2026-32638
StudioCMS is a server-side-rendered, Astro native, headless content …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/withstudiocms/studiocms/commit/aebe8bcb3618bb07c6753e3f5c982c1fe6adea64
- github.com/withstudiocms/studiocms/releases/tag/[email protected]
- github.com/withstudiocms/studiocms/security/advisories/GHSA-xvf4-ch4q-2m24
- nvd.nist.gov/vuln/detail/CVE-2026-32638
- github.com/advisories/GHSA-xvf4-ch4q-2m24
- nvd.nist.gov/vuln/detail/CVE-2026-32638
- cve.org/CVERecord?id=CVE-2026-32638
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.