Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

phpMyAdmin ReCaptcha bypass

CVE-2015-6830GHSA-v6fh-vg22-r6cm

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (phpmyadmin/phpmyadmin 4.4.14.1, 4.3.13.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist phpmyadmin/phpmyadmin

    Affected
    >= 4.3.0, < 4.3.13.2>= 4.4.0, < 4.4.14.1
    Fixed in
    4.4.14.1, 4.3.13.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2015-6830: 10.43% estimated exploitation activity in the next 30 days; percentile 95.75 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-v6fh-vg22-r6cm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2015-6830

Advisory: phpMyAdmin ReCaptcha bypass
IDs: CVE-2015-6830, GHSA-v6fh-vg22-r6cm
Record: https://patchnext.com/advisories/cve-2015-6830 (revision 1, source checked 26 Oct 2026, 14:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: phpmyadmin/phpmyadmin 4.4.14.1, 4.3.13.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist phpmyadmin/phpmyadmin: affected >= 4.3.0, < 4.3.13.2; >= 4.4.0, < 4.4.14.1; fixed in 4.4.14.1, 4.3.13.2

## Suggested inspection (read-only)
- Packagist phpmyadmin/phpmyadmin: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on phpmyadmin/phpmyadmin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-v6fh-vg22-r6cm (GitHub-reviewed advisory GHSA-v6fh-vg22-r6cm lists affected ranges: Packagist phpmyadmin/phpmyadmin >=4.3.0 =4.4.0 <4.4.14.1)

Commands are suggestions: review each one before running it.

Loading voting…