Privilege escalation via unbound API token generation
Published Mar 10, 2026 · Updated Mar 10, 2026
Incorrect authorization in withStudioCMS StudioCMS before 0.4.0 allows remote authenticated users to obtain owner-level API access. The dashboard API-token POST handler passes the request body's user UUID directly to token creation without binding it to the authenticated session or validating the target role. Editor access is sufficient to mint a token for an owner or administrator and then read or modify data through that account's REST API permissions.
Summary
What happened
Incorrect authorization in withStudioCMS StudioCMS before 0.4.0 allows remote authenticated users to obtain owner-level API access. The dashboard API-token POST handler passes the request body's user UUID directly to token creation without binding it to the authenticated session or validating the target role. Editor access is sufficient to mint a token for an owner or administrator and then read or modify data through that account's REST API permissions.
The record
- CVE
- CVE-2026-30944
- Published
- Mar 10, 2026
- Updated
- Mar 10, 2026
- Vendor
- withStudioCMS
- Product
- StudioCMS
- Classifications
- CWE-863, CWE-639, T1078
- 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-667w-mmh7-mrr4 authenticated Editor 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