dbcve.org
FedoraOperating system · Fedoraproject

CVE-2020-10804

HIGH · 8.0 CVSS v3.1 Published 2020-03-22
Fix available
A fix is available. Upgrade to 4.9.5 / 5.0.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In phpMyAdmin 4.x before 4.9.5 and 5.x before 5.0.2, a SQL injection vulnerability was found in retrieval of the current username (in libraries/classes/Server/Privileges.php and libraries/classes/UserPassword.php). A malicious user with access to the server could create a crafted username, and then trick the victim into performing specific actions with that user account (such as editing its privileges).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in phpMyAdmin's username retrieval functionality in libraries/classes/Server/Privileges.php and libraries/classes/UserPassword.php. A malicious authenticated user can craft a username containing SQL injection payloads, then trick a victim with higher privileges (such as an admin) into performing actions like editing that user's privileges, causing the malicious SQL to execute in the victim's session context.

MitigationUpgrade phpMyAdmin to version 4.9.5 or 5.0.2 or later. As a temporary workaround, restrict server access to trusted users only and educate administrators about social engineering attempts involving crafted usernames.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FedoraOperating system
Affected:= 30= 31= 32
phpMyAdminApplication
Affected:>= 4.0.0, < 4.9.5>= 5.0.0, < 5.0.2
Backports SleApplication
Affected:= 15.0
LeapOperating system
Affected:= 15.1
Package HubApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed phpMyAdmin version
    Check the version.php file in the phpMyAdmin root directory, or look at the login page footer which displays the version number
    Affected if The installed version is less than 4.9.5 (for 4.x releases) or less than 5.0.2 (for 5.x releases)
  2. Locate vulnerable script files
    Check for the existence of libraries/classes/Server/Privileges.php and libraries/classes/UserPassword.php in the phpMyAdmin installation directory
    Affected if These files exist in versions before 4.9.5 or 5.0.2, indicating the vulnerable code is present
  3. Determine user creation privileges
    Review phpMyAdmin configuration (config.inc.php) and MySQL user privileges to see which users can create or rename database users
    Affected if Users other than administrators can create new MySQL users or rename their username, allowing them to inject SQL through username fields
  4. Verify privilege editing functionality exposure
    Confirm whether the Server Privileges page (privileges.php) is accessible to users with standard database access
    Affected if Lower-privileged users can trigger administrative actions on their accounts that cause admins to load the vulnerable privilege editing interface

You are affected if your phpMyAdmin version is below 4.9.5 or below 5.0.2 AND your server permits user account creation or renaming by untrusted users who could inject malicious SQL into usernames.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 4.9.5 / 5.0.2 or later
Fixed in 4.9.55.0.2
Interim mitigation

Upgrade phpMyAdmin to version 4.9.5 or 5.0.2 or later. As a temporary workaround, restrict server access to trusted users only and educate administrators about social engineering attempts involving crafted usernames.

Fix this in Fedora Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-10804 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-10804 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data