LiveActive security incident?Get immediate response
CVE Record

CVE-2020-22278: phpMyAdmin through 5.0.2 allows CSV injection via Export Section.

phpMyAdmin through 5.0.2 allows CSV injection via Export Section. NOTE: the vendor disputes this because "the CSV file is accurately generated based on the database contents.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This disputed CVE says phpMyAdmin through 5.0.2 can export CSV files containing database values that may trigger CSV injection concerns. Business risk depends on whether staff open exported CSVs in spreadsheet tools and whether database content can be influenced by untrusted users.

Executive priority

Handle as a workflow-dependent risk, not a confirmed emergency. Prioritize inventory and export-handling controls if phpMyAdmin through 5.0.2 is present, especially where untrusted data is exported and opened by staff.

Technical view

The record describes CSV injection in phpMyAdmin's Export section through version 5.0.2. The vendor disputes the issue, stating the CSV is generated accurately from database contents. The record has no CVSS, CWE, or named patch details in the supplied sources.

Likely exposure

Exposure is most relevant where phpMyAdmin versions through 5.0.2 are used and exported CSV files are opened in spreadsheet applications. Risk is lower where exports are restricted, database contents are trusted, or exported files are not opened interactively.

Exploitation context

The supplied sources do not show active exploitation, KEV listing, public exploit use, or exploitation prevalence. The issue is disputed by the vendor, so validation should focus on actual export workflows and business handling of CSV files.

Researcher notes

Evidence is thin: no CVSS, CWE, exploit status, or remediation is provided in the source bundle. The vendor dispute is important because the alleged behavior may reflect faithful CSV export of database content rather than a product-side transformation flaw.

Mitigation direction

  • Check current phpMyAdmin vendor guidance for disputed CVE-2020-22278 handling.
  • Upgrade phpMyAdmin if your deployed version is at or below 5.0.2.
  • Restrict phpMyAdmin export access to trusted administrators.
  • Treat exported CSVs from untrusted data as potentially unsafe before spreadsheet opening.
  • Prefer non-spreadsheet review workflows for risky exports where practical.

Validation and detection

  • Inventory phpMyAdmin deployments and confirm exact versions.
  • Identify teams that export CSV data from phpMyAdmin.
  • Review whether exported data can contain untrusted user-controlled values.
  • Confirm spreadsheet-opening workflows for phpMyAdmin CSV exports.
  • Document compensating controls around export permissions and file handling.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-22278 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.