How severe is CVE-2011-2506?

No CVSS score has been assigned to CVE-2011-2506 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2011-2506?

CVE-2011-2506 affects the following packages: phpmyadmin/phpmyadmin (Packagist), phpmyadmin/phpmyadmin (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2011-2506?

Update phpmyadmin/phpmyadmin to 3.3.10.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-2506 is resolved across your whole dependency graph.

How do I detect CVE-2011-2506 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phpmyadmin/phpmyadmin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2011-2506 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2011-2506?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2011-2506 can be triaged on real exposure rather than presence alone.

Is CVE-2011-2506 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2011-2506, including 2 documented proof-of-concept exploits on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2011-2506?

CVE-2011-2506 has an EPSS (Exploit Prediction Scoring System) score of 9.6%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2011-2506?

CVE-2011-2506 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2011-2506 published, and has it been updated?

CVE-2011-2506 was published on July 14, 2011 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2011-2506 — phpmyadmin/phpmyadmin

CVE-2011-2506 is a Code Injection vulnerability in phpmyadmin/phpmyadmin. 4 public exploit references exist, so weaponization risk is real. A fix is available for phpmyadmin/phpmyadmin — see the affected versions and patch details below.

phpMyAdmin vulnerable to static code injection

Also known asGHSA-p6h7-29r2-g88f

Published

Jul 14, 2011

Updated

Apr 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

4 known

Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

9.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

🐘phpmyadmin/phpmyadmin🐘phpmyadmin/phpmyadmin

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

setup/lib/ConfigGenerator.class.php in phpMyAdmin 3.x before 3.3.10.2 and 3.4.x before 3.4.3.1 does not properly restrict the presence of comment closing delimiters, which allows remote attackers to conduct static code injection attacks by leveraging the ability to modify the SESSION superglobal array.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`phpmyadmin/phpmyadmin`	≥ 3.0&&< 3.3.10.2	3.3.10.2`composer require phpmyadmin/phpmyadmin:^3.3.10.2`
🐘Packagist	`phpmyadmin/phpmyadmin`	≥ 3.4&&< 3.4.3.1	3.4.3.1`composer require phpmyadmin/phpmyadmin:^3.4.3.1`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-17510webappsphp✓ Verified

phpMyAdmin3 (pma3) - Remote Code Execution

by wofeiwo · Jul 8, 2011

Exploit-DB Source

EDB-17514webappsphp✓ Verified

phpMyAdmin 3.x - Swekey Remote Code Injection

by Mango · Jul 9, 2011

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phpmyadmin/phpmyadmin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update phpmyadmin/phpmyadmin to 3.3.10.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-2506 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2011-2506 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2011-2506. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2011-2506 in your dependencies?

O3 Security finds CVE-2011-2506 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works