How severe is GHSA-wv8g-fx9j-q2jg?

No CVSS score has been assigned to GHSA-wv8g-fx9j-q2jg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wv8g-fx9j-q2jg?

GHSA-wv8g-fx9j-q2jg affects the following packages: phpmyadmin/phpmyadmin (Packagist), phpmyadmin/phpmyadmin (Packagist), phpmyadmin/phpmyadmin (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-wv8g-fx9j-q2jg?

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

How do I detect GHSA-wv8g-fx9j-q2jg in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phpmyadmin/phpmyadmin. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-wv8g-fx9j-q2jg if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-wv8g-fx9j-q2jg?

O3 pinpoints whether GHSA-wv8g-fx9j-q2jg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-wv8g-fx9j-q2jg actively exploited in the wild?

No public exploit code has been indexed for GHSA-wv8g-fx9j-q2jg yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-wv8g-fx9j-q2jg?

GHSA-wv8g-fx9j-q2jg is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-wv8g-fx9j-q2jg published, and has it been updated?

GHSA-wv8g-fx9j-q2jg was published on May 17, 2022 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-wv8g-fx9j-q2jg

GHSA-wv8g-fx9j-q2jg is a Cross-site Scripting (XSS) vulnerability in phpmyadmin/phpmyadmin. O3 Security confirms whether GHSA-wv8g-fx9j-q2jg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

phpMyAdmin cross-site scripting Vulnerability via ENUM value

Also known asCVE-2014-7217

Published

May 17, 2022

Updated

Nov 29, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Blast Radius

3 pkgs affected

🐘phpmyadmin/phpmyadmin🐘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

Multiple cross-site scripting (XSS) vulnerabilities in phpMyAdmin 4.0.x before 4.0.10.4, 4.1.x before 4.1.14.5, and 4.2.x before 4.2.9.1 allow remote authenticated users to inject arbitrary web script or HTML via a crafted ENUM value that is improperly handled during rendering of the (1) table search or (2) table structure page, related to libraries/TableSearch.class.php and libraries/Util.class.php.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`phpmyadmin/phpmyadmin`	≥ 4.0.0&&< 4.0.10.4	4.0.10.4
🐘Packagist	`phpmyadmin/phpmyadmin`	≥ 4.1.0&&< 4.1.14.5	4.1.14.5
🐘Packagist	`phpmyadmin/phpmyadmin`	≥ 4.2.0&&< 4.2.9.1	4.2.9.1

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update phpmyadmin/phpmyadmin to 4.0.10.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wv8g-fx9j-q2jg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-wv8g-fx9j-q2jg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-wv8g-fx9j-q2jg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Multiple cross-site scripting (XSS) vulnerabilities in phpMyAdmin 4.0.x before 4.0.10.4, 4.1.x before 4.1.14.5, and 4.2.x before 4.2.9.1 allow remote authenticated users to inject arbitrary web script or HTML via a crafted ENUM value that is improperly handled during rendering of the (1) table search or (2) table structure page, related to `libraries/TableSearch.class.php` and `libraries/Util.class.php`.

O3 Security · Impact-Aware SCA

Is GHSA-wv8g-fx9j-q2jg in your dependencies?

O3 detects GHSA-wv8g-fx9j-q2jg across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works