Admin-account proliferation via incomplete REST rank check
Published Mar 11, 2026 · Updated Mar 11, 2026
Improper privilege management in withStudioCMS StudioCMS before 0.4.3 allows remote authenticated users to create peer admin accounts. The REST createUser handler compares rank strings only to reject owner creation and omits the Dashboard's ordered check against assigning an equal or higher rank. An admin API token is required; the resulting peer account can preserve administrative access after the original password or token is revoked.
Summary
What happened
Improper privilege management in withStudioCMS StudioCMS before 0.4.3 allows remote authenticated users to create peer admin accounts. The REST createUser handler compares rank strings only to reject owner creation and omits the Dashboard's ordered check against assigning an equal or higher rank. An admin API token is required; the resulting peer account can preserve administrative access after the original password or token is revoked.
The record
- CVE
- CVE-2026-32106
- Published
- Mar 11, 2026
- Updated
- Mar 11, 2026
- Vendor
- withStudioCMS
- Product
- StudioCMS
- Classifications
- CWE-269, T1136
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Mar 11, 2026CVE publishedPublication date reported by the CVE source.
- Mar 11, 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.3
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.
Public exploit references
- Authenticated REST createUser curl 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