Authenticated privilege escalation via unchecked admin writes
Published May 19, 2026 · Updated May 19, 2026
Missing authorization in CtrlPanel 1.1.1 and earlier allows remote authenticated users to bypass RBAC through direct write requests. Multiple admin controllers check permissions in create() or edit() but process corresponding store() or update() requests without equivalent server-side checks. Any authenticated account can alter API keys, billing objects, server ownership, or user roles and passwords, enabling full privilege escalation without admin write permissions.
Summary
What happened
Missing authorization in CtrlPanel 1.1.1 and earlier allows remote authenticated users to bypass RBAC through direct write requests. Multiple admin controllers check permissions in create() or edit() but process corresponding store() or update() requests without equivalent server-side checks. Any authenticated account can alter API keys, billing objects, server ownership, or user roles and passwords, enabling full privilege escalation without admin write permissions.
The record
- CVE
- CVE-2026-34358
- Published
- May 19, 2026
- Updated
- May 19, 2026
- Vendor
- CtrlPanel.gg
- Product
- CtrlPanel
- Classifications
- CWE-862, CWE-284, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 19, 2026CVE publishedPublication date reported by the CVE source.
- May 19, 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=< 1.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
- Authenticated direct-write request 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