CVE-2013-20005
Awaiting Analysis Awaiting Analysis - Queue
CSRF in Qool CMS 2.0 RC2 Enables Root Account Creation

Publication date: 2026-03-16

Last updated on: 2026-03-16

Assigner: VulnCheck

Description
Qool CMS 2.0 RC2 contains a cross-site request forgery vulnerability that allows attackers to perform administrative actions by tricking logged-in users into visiting malicious web pages. Attackers can forge POST requests to the /admin/adduser endpoint with parameters like username, password, email, and level to create root-level user accounts without user consent.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-16
Last Modified
2026-03-16
Generated
2026-05-06
AI Q&A
2026-03-16
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
qool_cms qool_cms 2.0_rc2
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

[{'type': 'paragraph', 'content': "CVE-2013-20005 is a Cross-Site Request Forgery (CSRF) vulnerability in Qool CMS version 2.0 RC2. It allows attackers to perform administrative actions by tricking logged-in users into visiting malicious web pages. Specifically, attackers can forge POST requests to the /admin/adduser endpoint with parameters like username, password, email, and level to create root-level user accounts without the user's consent."}, {'type': 'paragraph', 'content': 'This vulnerability arises because Qool CMS does not properly validate the authenticity of HTTP requests for administrative functions, enabling attackers to escalate privileges by exploiting logged-in users.'}, {'type': 'paragraph', 'content': 'Additionally, the system suffers from multiple persistent Cross-Site Scripting (XSS) vulnerabilities due to improper input sanitization in various administrative scripts, which can lead to execution of arbitrary HTML and JavaScript code.'}] [1, 2, 3]


How can this vulnerability impact me? :

This vulnerability can have serious impacts including unauthorized creation of root-level user accounts, which grants attackers full administrative control over the Qool CMS installation.

By exploiting this flaw, attackers can perform privileged actions without the knowledge or consent of legitimate administrators, potentially leading to complete compromise of the website.

The persistent XSS vulnerabilities can also allow attackers to inject malicious scripts that execute in the context of the affected site, potentially compromising user sessions, stealing sensitive data, or spreading malware.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by monitoring for unauthorized POST requests to the /admin/adduser endpoint that include parameters such as username, password, email, and level, which are used to create user accounts with elevated privileges.'}, {'type': 'paragraph', 'content': 'To detect exploitation attempts, you can analyze web server logs for suspicious POST requests targeting /admin/adduser with unusual or unexpected parameter values.'}, {'type': 'paragraph', 'content': 'Example commands to detect such activity might include using grep or similar tools on access logs to find POST requests to the vulnerable endpoint:'}, {'type': 'list_item', 'content': "grep 'POST /admin/adduser' /var/log/apache2/access.log"}, {'type': 'list_item', 'content': "grep 'username=' /var/log/apache2/access.log | grep '/admin/adduser'"}, {'type': 'paragraph', 'content': 'Additionally, monitoring for unexpected creation of new user accounts with high privilege levels in the CMS database may help detect exploitation.'}] [1, 2, 3]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include implementing CSRF protections such as adding anti-CSRF tokens to administrative forms and validating the origin of POST requests.

Restrict access to the /admin/adduser endpoint to trusted IP addresses or networks where possible.

Ensure that users with administrative privileges are educated about the risks of visiting untrusted websites while logged into the CMS.

If possible, update or patch Qool CMS to a version that addresses this vulnerability.

As a temporary measure, monitor and audit user accounts for unauthorized additions, especially those with root or admin level privileges.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart