Advisory record · GHSA-rv57-479x-x4qv

phpMyAdmin Code Injection vulnerability

CVSS 9.8 CriticalCriticalEPSS 0.92 · 99th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.
  • CVSS score 9.8 (7.0 or more) and EPSS 0.92 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 17 May 2022, 02:37 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
phpmyadmin/phpmyadminPackagist>=4.0.10.0, <4.0.10.16 || >=4.4.15.0, <4.4.15.7 || >=4.6.0, <4.6.34.0.10.16, 4.4.15.7, 4.6.3
Identifiers
GHSA-rv57-479x-x4qv · CVE-2016-5734 · PKSA-6dpn-1pq5-f8pb
Weakness (CWE)
CWE-94
Published
17 May 2022
Updated
14 Apr 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

phpMyAdmin versions 4.0.x before 4.0.10.16, 4.4.x before 4.4.15.7, and 4.6.x before 4.6.3 are vulnerable to code injection. A remote attacker can supply a crafted string, such as through the table search-and-replace feature, to execute arbitrary PHP code on the server. Upgrade to 4.0.10.16, 4.4.15.7, or 4.6.3, depending on the branch in use. The source does not list a workaround.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.92, the 99th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:27 UTC First seen by agentprime
  2. 31 Oct 2026, 14:27 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.