How severe is CVE-2010-4481?

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

Which packages are affected by CVE-2010-4481?

CVE-2010-4481 affects the following packages: phpmyadmin/phpmyadmin (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2010-4481?

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

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

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2010-4481 actively exploited in the wild?

No public exploit code has been indexed for CVE-2010-4481 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2010-4481?

CVE-2010-4481 has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 81th 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-2010-4481?

CVE-2010-4481 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2010-4481 published, and has it been updated?

CVE-2010-4481 was published on December 17, 2010 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-2010-4481 — phpmyadmin

CVE-2010-4481 is a Improper Authentication vulnerability in phpmyadmin/phpmyadmin. A fix is available for phpmyadmin/phpmyadmin — see the affected versions and patch details below.

phpMyAdmin allows remote attackers to bypass authentication and obtain sensitive information

Also known asGHSA-gmc7-jvv7-w245

Published

Dec 17, 2010

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs81th percentile — riskier than 81% 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

phpMyAdmin before 3.4.0-beta1 allows remote attackers to bypass authentication and obtain sensitive information via a direct request to phpinfo.php, which calls the phpinfo function.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`phpmyadmin/phpmyadmin`	all versions	3.4.0-beta1`composer require phpmyadmin/phpmyadmin:^3.4.0-beta1`

Affected Products

1 product · 65 configurations

Application

phpmyadminphpmyadmin

≤ 3.3.9.0

50 versions

2.11.02.11.1.02.11.1.12.11.1.22.11.2.02.11.2.12.11.2.22.11.3.02.11.4.02.11.5.02.11.5.12.11.5.2

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.0-beta1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-4481 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

phpMyAdmin before 3.4.0-beta1 allows remote attackers to bypass authentication and obtain sensitive information via a direct request to phpinfo.php, which calls the phpinfo function.

O3 Security · Impact-Aware SCA

Is CVE-2010-4481 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works