# CVE-2026-30945: StudioCMS: IDOR — Arbitrary API Token Revocation Leading to Denial of Service

> Authenticated editors can revoke any user's API tokens, causing denial of service for critical integrations and automations.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Mar 2026
- **Updated:** 10 Mar 2026
- **Also known as:** GHSA-8rgj-vrfr-6hqr

## What is CVE-2026-30945?

CVE-2026-30945 is a high-severity missing authorization vulnerability in withstudiocms studiocms, published on 10 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-30945?

2 open source packages ship an affected version, including studiocms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `studiocms` | npm | All versions | 0.4.0 |
| `studiocms` | npm | All versions | 0.4.0 |

Products: Studiocms Studiocms.

## How do I fix CVE-2026-30945?

Upgrade studiocms to 0.4.0 or later.

## Is CVE-2026-30945 being exploited?

There is no known exploitation of CVE-2026-30945 in the wild and no public exploit code.

Public exploit code:

- https://github.com/FilipeGaudard/CVE-2026-30945-PoC (github_poc): https://github.com/FilipeGaudard/CVE-2026-30945-PoC

## Other vulnerabilities in withstudiocms studiocms

- [CVE-2026-30944](https://insights.sbomify.com/CVE-2026-30944/): StudioCMS Affected by Privilege Escalation via Insecure API Token Generation (high 8.8)
- [CVE-2026-32101](https://insights.sbomify.com/CVE-2026-32101/): StudioCMS S3 Storage Manager Authorization Bypass via Missing `await` on Async Auth Check (high 7.6)
- [CVE-2026-32103](https://insights.sbomify.com/CVE-2026-32103/): StudioCMS: IDOR — Admin-to-Owner Account Takeover via Password Reset Link Generation (medium 6.8)
- [CVE-2026-24134](https://insights.sbomify.com/CVE-2026-24134/): StudioCMS has an Authorization Bypass Through User-Controlled Key (medium 6.5)
- [CVE-2026-32104](https://insights.sbomify.com/CVE-2026-32104/): StudioCMS: IDOR in User Notification Preferences Allows Any Authenticated User to Modify Any User's Settings (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-30945 and fix it if it is affected.

What it is: CVE-2026-30945 is a high-severity missing authorization vulnerability in withstudiocms studiocms, published on 10 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-30945 in the wild and no public exploit code.

Affected packages and fixed versions:
- studiocms (npm): affected all versions; fixed in 0.4.0
- studiocms (npm): affected all versions; fixed in 0.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-30945/ (Markdown: https://insights.sbomify.com/CVE-2026-30945/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-30945
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-30945
- OSV: https://osv.dev/vulnerability/CVE-2026-30945

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-30945/
Summaries are generated and may contain mistakes; the official description above is the record.