Skip to content

GHSA-2p7v-jm8m-g3qq CVE-2016-5739

phpMyAdmin vulnerable to Cross-Site Request Forgery

High Packagist
Severity
7.5 / 10
High · CVSS 3.0
Exploit chance (EPSS)
2.95%
Chance of exploitation in the next 30 days. Higher than 87.16% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
4.0.10.16
Upgrade phpmyadmin/phpmyadmin to this version or later

Description

The Transformation implementation in phpMyAdmin 4.0.x before 4.0.10.16, 4.4.x before 4.4.15.7, and 4.6.x before 4.6.3 does not use the no-referrer Content Security Policy (CSP) protection mechanism, which makes it easier for remote attackers to conduct CSRF attacks by reading an authentication token in a Referer header, related to libraries/Header.php.

Affected versions

Packagist

PackageVulnerableFixed in
phpmyadmin/phpmyadmin
>= 4.0.10.0, < 4.0.10.16
4.0.10.16
phpmyadmin/phpmyadmin
>= 4.4.15.0, < 4.4.15.7
4.4.15.7
phpmyadmin/phpmyadmin
>= 4.6.0, < 4.6.3
4.6.3

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

phpmyadmin/phpmyadmin Packagist → 4.0.10.16

composer
composer require phpmyadmin/phpmyadmin:^4.0.10.16

Severity breakdown

CVSS 3.0 7.5

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-222v-cx2c-q2f5
phpMyAdmin XSS when checking tables
Medium Also affects phpmyadmin/phpmyadmin
GHSA-6hr3-44gx-g6wh
Cross-site Scripting vulnerability in drag-and-drop upload of phpMyAdmin
Medium Also affects phpmyadmin/phpmyadmin
GHSA-prcg-mc23-hgjh
phpmyadmin contains SQL Injection vulnerability
Critical Also affects phpmyadmin/phpmyadmin
GHSA-4c9q-64gq-xhx4
phpMyAdmin Cross-Site Request Forgery (CSRF)
Medium Also affects phpmyadmin/phpmyadmin
GHSA-7ff4-cv53-4cjq
phpMyAdmin SQL injection vulnerability
Critical Also affects phpmyadmin/phpmyadmin
GHSA-6349-53vr-7hcr
phpMyAdmin Cross-site Scripting (XSS)
Medium Also affects phpmyadmin/phpmyadmin
GHSA-h65r-8fp8-w7cx
phpMyAdmin SQL Injection
High Also affects phpmyadmin/phpmyadmin
GHSA-fcww-8wvc-38q9
phpMyAdmin SQL injection vulnerability
Medium Also affects phpmyadmin/phpmyadmin
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor