How severe is GHSA-567r-vqj7-5cw7?

GHSA-567r-vqj7-5cw7 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-567r-vqj7-5cw7?

GHSA-567r-vqj7-5cw7 affects the following packages: phpmyadmin/phpmyadmin (Packagist), phpmyadmin/phpmyadmin (Packagist), phpmyadmin/phpmyadmin (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-567r-vqj7-5cw7?

Update phpmyadmin/phpmyadmin to 4.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-567r-vqj7-5cw7 is resolved across your whole dependency graph.

How do I detect GHSA-567r-vqj7-5cw7 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-567r-vqj7-5cw7 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-567r-vqj7-5cw7?

O3 pinpoints whether GHSA-567r-vqj7-5cw7 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-567r-vqj7-5cw7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-567r-vqj7-5cw7 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-567r-vqj7-5cw7?

GHSA-567r-vqj7-5cw7 is classified as CWE-254 (CWE-254). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-567r-vqj7-5cw7 published, and has it been updated?

GHSA-567r-vqj7-5cw7 was published on May 17, 2022 and was last updated on November 30, 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-567r-vqj7-5cw7

CRITICAL

GHSA-567r-vqj7-5cw7 is a critical-severity (CVSS 9.8) CWE-254 vulnerability in phpmyadmin/phpmyadmin. O3 Security confirms whether GHSA-567r-vqj7-5cw7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

phpMyAdmin Authentication Bypass

Also known asCVE-2016-6629

Published

May 17, 2022

Updated

Nov 30, 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

An issue was discovered in phpMyAdmin involving the $cfg['ArbitraryServerRegexp'] configuration directive. An attacker could reuse certain cookie values in a way of bypassing the servers defined by ArbitraryServerRegexp. All 4.6.x versions (prior to 4.6.4), 4.4.x versions (prior to 4.4.15.8), and 4.0.x versions (prior to 4.0.10.17) are affected.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`phpmyadmin/phpmyadmin`	≥ 4.6&&< 4.6.4	4.6.4
🐘Packagist	`phpmyadmin/phpmyadmin`	≥ 4.4&&< 4.4.15.8	4.4.15.8
🐘Packagist	`phpmyadmin/phpmyadmin`	≥ 4.0&&< 4.0.10.17	4.0.10.17

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.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-567r-vqj7-5cw7 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-567r-vqj7-5cw7 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-567r-vqj7-5cw7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue was discovered in phpMyAdmin involving the `$cfg['ArbitraryServerRegexp']` configuration directive. An attacker could reuse certain cookie values in a way of bypassing the servers defined by ArbitraryServerRegexp. All 4.6.x versions (prior to 4.6.4), 4.4.x versions (prior to 4.4.15.8), and 4.0.x versions (prior to 4.0.10.17) are affected.

O3 Security · Impact-Aware SCA

Is GHSA-567r-vqj7-5cw7 in your dependencies?

O3 detects GHSA-567r-vqj7-5cw7 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