How severe is CVE-2011-1941?

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

Which packages are affected by CVE-2011-1941?

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

How do I fix CVE-2011-1941?

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

How do I detect CVE-2011-1941 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-1941 if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

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

Yes. There are 2 known exploit references for CVE-2011-1941, including 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-1941?

CVE-2011-1941 has an EPSS (Exploit Prediction Scoring System) score of 1.9%, placing it in the 80th 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-1941?

CVE-2011-1941 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2011-1941 was published on January 26, 2012 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-1941 — phpmyadmin

Fix: phpmyadmin/composer@b7a8179

CVE-2011-1941 is a Improper Input Validation vulnerability in phpmyadmin/phpmyadmin. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for phpmyadmin/phpmyadmin — see the affected versions and patch details below.

phpMyAdmin Open Redirect in redirector

Also known asGHSA-v6fw-xf2c-8q43

Published

Jan 26, 2012

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs80th percentile — riskier than 80% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘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

Open redirect vulnerability in the redirector feature in phpMyAdmin 3.4.x before 3.4.1 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via unspecified vectors.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`phpmyadmin/phpmyadmin`	≥ 3.4.0&&< 3.4.1	3.4.1`composer require phpmyadmin/phpmyadmin:^3.4.1`

Affected Products

1 product · 1 configurations

Application

phpmyadminphpmyadmin

1 version

3.4.0.0

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.

Open redirect vulnerability in the redirector feature in phpMyAdmin 3.4.…

phpmyadmin.git.sourceforge.netNVDFeb 2012

Report on phpmyadmin.git.sourceforge.net

phpmyadmin.git.sourceforge.netNVDFeb 2012

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.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-1941 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2011-1941 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works