StudioCMS: IDOR — Arbitrary API Token Revocation Leading to Denial of Service

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

EPSS

• CVE-2026-30945: 0.48% estimated exploitation activity in the next 30 days; percentile 41.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The DELETE /studiocmsapi/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. Details Vulnerable Code The following is the server-side handler for the DELETE /studiocmsapi/dashboard/api-tokens endpoint (revokeApiToken): File: packages/studiocms/frontend/pages/studiocmsapi/dashboard/api-tokens.ts (lines 58–99) Version: studiocms@0.3.0 Analysis The handler shares the same class of authorization flaws found in the token generation endpoint, applied to a destructive operation: 1. Insufficient permission gate [1][2][3]: The handler retrieves the session from ctx.locals.StudioCMS.security and only checks isEditor. Token revocation…

Published by the source

11 Mar 2026, 00:16 UTC

Last modified by the source

13 Mar 2026, 04:42 UTC

Source last checked

26 Oct 2026, 12:43 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-8rgj-vrfr-6hqr

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-8rgj-vrfr-6hqr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-30945

Advisory: StudioCMS: IDOR — Arbitrary API Token Revocation Leading to Denial of Service
IDs: CVE-2026-30945, GHSA-8rgj-vrfr-6hqr
Record: https://patchnext.com/advisories/cve-2026-30945 (revision 2, source checked 26 Oct 2026, 12:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: studiocms 0.4.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm studiocms: affected <= 0.3.0; fixed in 0.4.0

## Suggested inspection (read-only)
- `npm ls studiocms --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on studiocms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-8rgj-vrfr-6hqr (OSV record GHSA-8rgj-vrfr-6hqr lists affected ranges: npm studiocms >=0 <0.4.0 (fixed))
- Verified: https://github.com/advisories/GHSA-8rgj-vrfr-6hqr (GitHub-reviewed advisory GHSA-8rgj-vrfr-6hqr lists affected ranges: npm studiocms >=0 <=0.3.0)

Commands are suggestions: review each one before running it.