Owner account disclosure via query-controlled rank filtering
Published Mar 18, 2026 · Updated Mar 18, 2026
Authorization bypass in StudioCMS before 0.4.4 allows remote authenticated users with admin tokens to read owner account records. The getUsers handler tests the attacker-controlled rank query parameter instead of the caller's rank, so rank=owner skips owner filtering. An admin-level REST API token and an enabled REST API are required; the response discloses owner IDs, usernames, display names, and email addresses but does not alter records.
Summary
What happened
Authorization bypass in StudioCMS before 0.4.4 allows remote authenticated users with admin tokens to read owner account records. The getUsers handler tests the attacker-controlled rank query parameter instead of the caller's rank, so rank=owner skips owner filtering. An admin-level REST API token and an enabled REST API are required; the response discloses owner IDs, usernames, display names, and email addresses but does not alter records.
The record
- CVE
- CVE-2026-32638
- Published
- Mar 18, 2026
- Updated
- Mar 18, 2026
- Vendor
- StudioCMS
- Product
- StudioCMS
- Classifications
- CWE-639, T1087
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Mar 18, 2026CVE publishedPublication date reported by the CVE source.
- Mar 18, 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.4
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
- Authenticated getUsers owner-enumeration HTTP PoCproof 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