Skip to content
Fencer Intel
medium 5.0

CVE-2015-6830 json

phpMyAdmin ReCaptcha bypass

published 2015-09-14 11 y ago modified 2026-06-17 4 mo ago also GHSA-v6fh-vg22-r6cm , EUVD-2022-5294

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
10.4%
EPSS 10.4% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

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.

Patch / fix

  • packagist phpmyadmin/phpmyadmin 4.3.13.2, 4.4.14.1
  • phpmyadmin Debian 14, Debian 13, Debian 12 4:4.4.14.1-1

debian advisories DEBIAN-CVE-2015-6830

  • phpMyAdmin openSUSE Tumbleweed 4.6.5.2-1.1

opensuse advisories openSUSE-SU-2024:10054-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-6830 updated cvss 4.0

phpMyAdmin: Bypassing the reCaptcha test

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. Published
  2. First public exploit (EDB-52414)

Exploit prediction

10.43% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-52414 PHPMyAdmin 3.0 - Bruteforce Login Bypass remote, 2025-08-18

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Affected packages

ecosystem package affected fixed in
packagist phpmyadmin/phpmyadmin
>=4.3.0, <4.3.13.2
>=4.4.0, <4.4.14.1
4.3.13.2
4.4.14.1

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.