# CVE-2013-20005: Qool CMS 2.0 RC2 Cross-Site Request Forgery via adduser

> Attackers can create root-level user accounts in Qool CMS by tricking logged-in administrators into visiting malicious pages.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2026
- **Updated:** 16 Mar 2026
- **Also known as:** GHSA-gx9f-52wg-g9gm

## What is CVE-2013-20005?

CVE-2013-20005 is a medium-severity vulnerability in Qool CMS, published on 15 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2013-20005?


## How do I fix CVE-2013-20005?

No fix has been published for CVE-2013-20005 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-20005 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-20005 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-20005 and fix it if it is affected.

What it is: CVE-2013-20005 is a medium-severity vulnerability in Qool CMS, published on 15 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-20005 exists.

Affected product: Qool CMS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-20005/ (Markdown: https://insights.sbomify.com/CVE-2013-20005/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-20005
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-20005
- OSV: https://osv.dev/vulnerability/CVE-2013-20005

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-20005/
Summaries are generated and may contain mistakes; the official description above is the record.