CVE-2011-10013
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTraq 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe vulnerability exists in the authorization logic of admincp/common.php in Traq versions 2.0-2.3. The flawed logic fails to halt script execution after a failed access check, allowing unauthenticated attackers to bypass authentication and reach admin-only functionality. This can be exploited through plugins.php to inject and execute arbitrary PHP code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Traq installation and versionLocate the Traq installation directory and find the version file (typically version.php in the includes folder or displayed in the admin area). Read the version number from the file.Affected if Installed version is 2.0, 2.1, 2.2, or 2.3
-
Verify vulnerable file existsCheck if the file admincp/common.php exists in the Traq installation directory.Affected if The file admincp/common.php exists in Traq versions 2.0-2.3
-
Examine authorization logic in admincp/common.phpOpen admincp/common.php and locate the access control or authentication check code. Look for whether the script properly terminates (exit, die, or redirect) after a failed access check.Affected if The code shows that execution continues after a failed authentication check (missing exit/die/redirect after auth failure)
-
Test admin access without authenticationAttempt to access admincp functionality directly via HTTP request without providing any valid admin session or credentials.Affected if Admin-only functions in admincp are accessible without authentication
-
Check plugins.php accessibilityAttempt to access plugins.php without being logged in as an administrator to see if unauthenticated access is possible.Affected if plugins.php is reachable without authentication and can be used to inject arbitrary PHP code
A Traq installation is affected if it is version 2.0-2.3, contains admincp/common.php, and allows access to admin functions or plugins.php without valid authentication credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Traq to a version beyond 2.3 or apply the vendor patch to fix the authorization bypass in admincp/common.php that allows unauthenticated access to admin functions.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-10013 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-10013 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data