How severe is GHSA-v6fh-vg22-r6cm?

No CVSS score has been assigned to GHSA-v6fh-vg22-r6cm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v6fh-vg22-r6cm?

GHSA-v6fh-vg22-r6cm affects the following packages: phpmyadmin/phpmyadmin (Packagist), phpmyadmin/phpmyadmin (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-v6fh-vg22-r6cm?

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

How do I detect GHSA-v6fh-vg22-r6cm 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 GHSA-v6fh-vg22-r6cm 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 GHSA-v6fh-vg22-r6cm actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-v6fh-vg22-r6cm, 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 GHSA-v6fh-vg22-r6cm?

GHSA-v6fh-vg22-r6cm 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 GHSA-v6fh-vg22-r6cm?

GHSA-v6fh-vg22-r6cm 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 GHSA-v6fh-vg22-r6cm published, and has it been updated?

GHSA-v6fh-vg22-r6cm was published on May 17, 2022 and was last updated on November 8, 2023. 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

phpMyAdmin ReCaptcha bypassGHSA-v6fh-vg22-r6cm

Fix: phpmyadmin/phpmyadmin@0314e67

GHSA-v6fh-vg22-r6cm 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.

Also known asCVE-2015-6830

Published

May 17, 2022

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

10.4%probability of exploitation in next 30 days

Moderate Risk0.00%

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 GHSA-v6fh-vg22-r6cm 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 GHSA-v6fh-vg22-r6cm in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works