Auth bypass in Studiocms
CVE-2026-30945
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.
Vulnerability class: IDOR (Insecure Direct Object Reference)
EPSS: 0.005 (36.9th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 7.1 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H.
Affected products
- Studiocms
- Withstudiocms Studiocms — versions < 0.4.0
Weakness classification (CWE)
Public proof-of-concept exploits
References
- security-advisories@github.com (x_refsource_CONFIRM, Exploit, Vendor Advisory)
- security-advisories@github.com (Patch, x_refsource_MISC)
- security-advisories@github.com (Product, x_refsource_MISC)
Frequently asked questions
- What is CVE-2026-30945?
- CVE-2026-30945 is a high-severity vulnerability in Studiocms, classified under Authorization Bypass Through User-Controlled Key. CVSS score: 7.1/10. Published 2026-03-10.
- How severe is CVE-2026-30945?
- High severity. CVSS v3 base score is 7.1 out of 10.
- Is CVE-2026-30945 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.