# CVE-2013-20006: Qool CMS Multiple Persistent Cross-Site Scripting Vulnerabilities

> Attackers can inject malicious scripts via unsanitized POST parameters in Qool CMS admin panels, potentially compromising administrator sessions.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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-v9gc-c4r9-gw5c

## What is CVE-2013-20006?

CVE-2013-20006 is a high-severity cross-site scripting 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 contains multiple persistent cross-site scripting vulnerabilities in several administrative scripts where POST parameters are not properly sanitized before being stored and returned to users. Attackers can inject malicious JavaScript code through parameters like 'title', 'name', 'email', 'username', 'link', and 'task' in endpoints such as addnewtype, addnewdatafield, addmenu, addusergroup, addnewuserfield, adduser, addgeneraldata, and addcontentitem to execute arbitrary scripts in administrator browsers.

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

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


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

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

## Is CVE-2013-20006 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-20006 is a high-severity cross-site scripting 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-20006 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-20006/ (Markdown: https://insights.sbomify.com/CVE-2013-20006/index.md)
```

## Sources

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

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