# CVE-2011-10013: Traq 2.0–2.3 admincp/common.php RCE

> Unauthenticated attackers can bypass authorization checks in Traq to execute arbitrary PHP code via the admin panel.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2025
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-wjrf-v3xh-x8jw

## What is CVE-2011-10013?

CVE-2011-10013 is a critical authentication bypass vulnerability in Traq Project Issue Tracking System, published on 13 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Traq versions 2.0 through 2.3 contain a remote code execution vulnerability in the admincp/common.php script. The flawed authorization logic fails to halt execution after a failed access check, allowing unauthenticated users to reach admin-only functionality. This can be exploited via plugins.php to inject and execute arbitrary PHP code.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2011-10013?


## How do I fix CVE-2011-10013?

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

## Is CVE-2011-10013 being exploited?

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

Public exploit code:

- Traq admincp/common.php Remote Code Execution (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-10013 and fix it if it is affected.

What it is: CVE-2011-10013 is a critical authentication bypass vulnerability in Traq Project Issue Tracking System, published on 13 Aug 2025. 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-2011-10013 exists.

Affected product: Traq Project Issue Tracking System. 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-2011-10013/ (Markdown: https://insights.sbomify.com/CVE-2011-10013/index.md)
```

## Sources

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

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