CVE-2026-30945
High · 7.1CVSS
7.1
EPSS
0.5%
Published
Mar 10, 2026
CISA due date
—
The record
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.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| npm | studiocms | 0 | 0.4.0 |
Related vulnerabilities
- GHSA-8rgj-vrfr-6hqr StudioCMS: IDOR — Arbitrary API Token Revocation Leading to Denial of Service Same vulnerability
- CVE-2026-32638 StudioCMS is a server-side-rendered, Astro native, headless content management system. Also affects studiocms
- GHSA-xvf4-ch4q-2m24 StudioCMS REST getUsers Exposes Owner Account Records to Admin Tokens Also affects studiocms
- GHSA-wj56-g96r-673q StudioCMS: REST API Missing Rank Check Allows Admin to Create Peer Admin Accounts Also affects studiocms
- GHSA-9v82-xrm4-mp52 StudioCMS: IDOR in User Notification Preferences Allows Any Authenticated User to Modify… Also affects studiocms
- GHSA-h7vr-cg25-jf8c StudioCMS: IDOR — Admin-to-Owner Account Takeover via Password Reset Link Generation Also affects studiocms
- CVE-2026-32106 StudioCMS is a server-side-rendered, Astro native, headless content management system. Also affects studiocms
- CVE-2026-32103 StudioCMS is a server-side-rendered, Astro native, headless content management system. Also affects studiocms