CVE-2026-30945
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.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.
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/9eec9c3b45523b635cfe16d55aa55afabacbebe3
- github.com/withstudiocms/studiocms/releases/tag/[email protected]
- github.com/withstudiocms/studiocms/security/advisories/GHSA-8rgj-vrfr-6hqr
- nvd.nist.gov/vuln/detail/CVE-2026-30945
- github.com/advisories/GHSA-8rgj-vrfr-6hqr
- nvd.nist.gov/vuln/detail/CVE-2026-30945
- cve.org/CVERecord?id=CVE-2026-30945
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.