CVE-2026-30945
Privilege Escalation in StudioCMS API Token Revocation Endpoint
Publication date: 2026-03-10
Last updated on: 2026-03-17
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| studiocms | studiocms | to 0.4.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
| CWE-639 | The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability exists in StudioCMS versions prior to 0.4.0 in the DELETE /studiocms_api/dashboard/api-tokens endpoint. Any authenticated user with editor privileges or higher can revoke API tokens belonging to other users, including those of admin and owner accounts. This happens because the endpoint accepts tokenID and userID directly from the request payload without verifying token ownership, the caller's identity, or role hierarchy.
As a result, an attacker with editor or higher privileges can revoke critical API tokens of other users, potentially disrupting integrations and automations.
How can this vulnerability impact me? :
This vulnerability can lead to a targeted denial of service against important integrations and automations by allowing an attacker to revoke API tokens of other users, including administrators and owners.
Such disruptions can affect system availability and operational continuity, especially if critical API tokens are revoked unexpectedly.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade StudioCMS to version 0.4.0 or later, where the issue is fixed.
Until the upgrade is applied, restrict editor privileges to trusted users only, as any authenticated user with editor privileges or above can revoke API tokens of other users.
Monitor and audit API token revocation requests to detect any suspicious activity targeting critical integrations and automations.