Integration denial via unchecked API token revocation
Published Mar 10, 2026 · Updated Mar 10, 2026
Incorrect authorization in StudioCMS before 0.4.0 allows remote authenticated users to revoke API tokens belonging to other users. The dashboard API-token DELETE handler passes request-supplied tokenID and userID values to the deletion operation without checking ownership, caller identity, or role hierarchy. Editor privileges are sufficient to invalidate tokens owned by administrators or owners, interrupting integrations and automated workflows that depend on them.
Summary
What happened
Incorrect authorization in StudioCMS before 0.4.0 allows remote authenticated users to revoke API tokens belonging to other users. The dashboard API-token DELETE handler passes request-supplied tokenID and userID values to the deletion operation without checking ownership, caller identity, or role hierarchy. Editor privileges are sufficient to invalidate tokens owned by administrators or owners, interrupting integrations and automated workflows that depend on them.
The record
- CVE
- CVE-2026-30945
- Published
- Mar 10, 2026
- Updated
- Mar 10, 2026
- Vendor
- withStudioCMS
- Product
- StudioCMS
- Classifications
- CWE-863, CWE-639, T1531
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 10, 2026CVE publishedPublication date reported by the CVE source.
- Mar 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-8rgj-vrfr-6hqr embedded proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo