Vulnerability Description
StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.0, the DELETE /studiocms_api/dashboard/api-tokens endpoint allows any authenticated user with editor privileges or above to revoke API tokens belonging to any other user, including admin and owner accounts. The handler accepts tokenID and userID directly from the request payload without verifying token ownership, caller identity, or role hierarchy. This enables targeted denial of service against critical integrations and automations. This vulnerability is fixed in 0.4.0.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Studiocms | Studiocms | < 0.4.0 |
Related Weaknesses (CWE)
References
- https://github.com/withstudiocms/studiocms/commit/9eec9c3b45523b635cfe16d55aa55aPatch
- https://github.com/withstudiocms/studiocms/releases/tag/[email protected]Product
- https://github.com/withstudiocms/studiocms/security/advisories/GHSA-8rgj-vrfr-6hExploitVendor Advisory
FAQ
What is CVE-2026-30945?
CVE-2026-30945 is a vulnerability with a CVSS score of 7.1 (HIGH). StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.0, the DELETE /studiocms_api/dashboard/api-tokens endpoint allows any authenticated user with editor...
How severe is CVE-2026-30945?
CVE-2026-30945 has been rated HIGH with a CVSS base score of 7.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-30945?
Check the references section above for vendor advisories and patch information. Affected products include: Studiocms Studiocms.