How severe is CVE-2015-6830?

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

Which packages are affected by CVE-2015-6830?

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

How do I fix CVE-2015-6830?

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

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

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2015-6830 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2015-6830, including 1 documented proof-of-concept exploit on Exploit-DB. 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-2015-6830?

CVE-2015-6830 has an EPSS (Exploit Prediction Scoring System) score of 10.4%, placing it in the 96th 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2015-6830?

CVE-2015-6830 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-6830 published, and has it been updated?

CVE-2015-6830 was published on September 14, 2015 and was last updated on April 16, 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-2015-6830 — phpmyadmin

Fix: phpmyadmin/phpmyadmin@785f4e2

CVE-2015-6830 is a Information Exposure vulnerability in phpmyadmin/phpmyadmin. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for phpmyadmin/phpmyadmin — see the affected versions and patch details below.

phpMyAdmin ReCaptcha bypass

Also known asGHSA-v6fh-vg22-r6cm

Published

Sep 14, 2015

Updated

Apr 16, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

10.4%probability of exploitation in next 30 days

Moderate Risk+0.64%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

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

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

libraries/plugins/auth/AuthenticationCookie.class.php in phpMyAdmin 4.3.x before 4.3.13.2 and 4.4.x before 4.4.14.1 allows remote attackers to bypass a multiple-reCaptcha protection mechanism against brute-force credential guessing by providing a correct response to a single reCaptcha.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`phpmyadmin/phpmyadmin`	≥ 4.3.0&&< 4.3.13.2	4.3.13.2`composer require phpmyadmin/phpmyadmin:^4.3.13.2`
🐘Packagist	`phpmyadmin/phpmyadmin`	≥ 4.4.0&&< 4.4.14.1	4.4.14.1`composer require phpmyadmin/phpmyadmin:^4.4.14.1`

Affected Products

1 product · 31 configurations

Application

phpmyadminphpmyadmin

31 versions

4.3.04.3.14.3.24.3.34.3.44.3.54.3.64.3.74.3.84.3.94.3.104.3.11

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-52414remotephp

PHPMyAdmin 3.0 - Bruteforce Login Bypass

by Nikola Markovic · Aug 18, 2025

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 4.3.13.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-6830 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-6830 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works