Draft disclosure via unchecked content UUID
Published Jan 27, 2026 · Updated Jan 27, 2026
Authorization bypass in withStudioCMS StudioCMS before 0.2.0 allows remote authenticated users to read other users' draft content. The content-management edit route accepts a user-controlled draft UUID after checking only authentication, without enforcing the Editor role or verifying draft ownership. A Visitor account and a valid draft UUID are sufficient to disclose unpublished content; no write or service-interruption impact is reported.
Summary
What happened
Authorization bypass in withStudioCMS StudioCMS before 0.2.0 allows remote authenticated users to read other users' draft content. The content-management edit route accepts a user-controlled draft UUID after checking only authentication, without enforcing the Editor role or verifying draft ownership. A Visitor account and a valid draft UUID are sufficient to disclose unpublished content; no write or service-interruption impact is reported.
The record
- CVE
- CVE-2026-24134
- Published
- Jan 27, 2026
- Updated
- Jan 27, 2026
- Vendor
- withStudioCMS
- Product
- StudioCMS
- Classifications
- CWE-862, CWE-639, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 27, 2026CVE publishedPublication date reported by the CVE source.
- Jan 27, 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.2.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-8cw6-53m5-4932 Visitor-role reproductionproof 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