Root account creation via forged adduser request
Published Mar 15, 2026 · Updated Mar 16, 2026
Cross-site request forgery in Qool CMS 2.0 RC2 allows context-dependent attackers to create root-level accounts via /admin/adduser. The /admin/adduser handler accepts username, password, email, and level in a POST request without checking that the logged-in user initiated it. A logged-in administrator must visit attacker-controlled content, after which the forged level=1 request adds an account with root privileges.
Summary
What happened
Cross-site request forgery in Qool CMS 2.0 RC2 allows context-dependent attackers to create root-level accounts via /admin/adduser. The /admin/adduser handler accepts username, password, email, and level in a POST request without checking that the logged-in user initiated it. A logged-in administrator must visit attacker-controlled content, after which the forged level=1 request adds an account with root privileges.
The record
- CVE
- CVE-2013-20005
- Published
- Mar 15, 2026
- Updated
- Mar 16, 2026
- Vendor
- Qool
- Product
- Qool CMS
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 15, 2026CVE publishedPublication date reported by the CVE source.
- Mar 16, 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=2.0
What conditions does exploitation require?
What is affected?
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
- Qool CMS XSRF Add Root Exploitfunctional · 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