StudioCMS
StudioCMS: IDOR — Arbitrary API Token Revocation Leading to Denial of Service
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.4.0
Fixed in 0.4.0
Mitigation
Upgrade studiocms to 0.4.0 or later.
References
- Vendor advisory github.com/withstudiocms/studiocms/security/ad…
- Patch github.com/withstudiocms/studiocms/commit/9eec…
- Release notes github.com/withstudiocms/studiocms/releases/ta…
Timeline
Days relative to CVE publicationFirst public PoC 1.2 days after publication; not in CISA KEV. First PoC: FilipeGaudard/CVE-2026-30945-PoC (created 11 Mar 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| FilipeGaudard/CVE-2026-30945-PoC | 11 Mar 2026 +1.2 d | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.