CVE-2026-119426

phpMyAdmin through 5.2.3 CSRF Token Bypass via Non-AJAX POST to /sql

Published Oct 30, 2026 CVSS 4.0 · 7.7 High EPSS < 1% KEV · Not listed
Description
phpMyAdmin through 5.2.3 contains a cross-site request forgery vulnerability that allows remote attackers to execute arbitrary SQL by bypassing CSRF token checks on non-AJAX POST requests. Attackers can lure authenticated victims into submitting cross-site POSTs carrying sql_query to /sql or /database/sql, running SQL with the victim's database privileges under http or config authentication.

Analysis

AI-generated

Technical impact

The vulnerability allows remote attackers to bypass the CSRF token check on non‑AJAX POST requests to the /sql endpoint in phpMyAdmin, enabling the execution of arbitrary SQL statements under the victim’s database privileges. This flaw effectively permits attackers to read, modify, or delete data in databases accessed by the authenticated user, potentially leading to data compromise, privacy violations, or further lateral movement. The weakness is classified as a CSRF (Common Weakness Enumeration 352) vulnerability.

Affected Systems

The flaw affects all releases of phpMyAdmin up to and including version 5.2.3. Administrators using phpMyAdmin 5.2.3 or earlier should review installed versions and plan an upgrade. The affected product is the phpMyAdmin web interface, which may be deployed in various client‑side or server‑side configurations.

Risk and Exploitability

The CVSS score of 7.7 indicates high severity, and the EPSS score of < 1% indicates a very low exploitation probability; the KEV listing absence suggests there has been no widespread exploitation yet. The attack requires a victim to be authenticated and to perform a non‑AJAX POST to /sql or /database/sql, typically by tricking them through a crafted link or form. Once the attacker supplies the sql_query parameter, any valid SQL can be executed with the victim’s privileges, allowing a wide range of attacks from data exfiltration to privilege escalation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to phpMyAdmin version 5.2.4 or later, which contains the CSRF fix.
  • If an upgrade is not immediately possible, apply the security patch from commit 910322373f14ed4601c85234858f630f127569ef (and d1e2b54b530685c24dd91181b9f64a5a64621789) to the phpMyAdmin source code.
  • As a temporary workaround, block non‑AJAX POST requests to /sql and /database/sql by configuring a web‑application firewall or the web server to reject such requests unless an X‑Requested‑With header is present.

Generated by OpenCVE AI on November 4, 2026 at 10:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description phpMyAdmin through 5.2.3 contains a cross-site request forgery vulnerability that allows remote attackers to execute arbitrary SQL by bypassing CSRF token checks on non-AJAX POST requests. Attackers can lure authenticated victims into submitting cross-site POSTs carrying sql_query to /sql or /database/sql, running SQL with the victim's database privileges under http or config authentication.
Title phpMyAdmin through 5.2.3 CSRF Token Bypass via Non-AJAX POST to /sql
First Time appeared Phpmyadmin
Phpmyadmin phpmyadmin
Weaknesses CWE-352
CPEs cpe:2.3:a:phpmyadmin:phpmyadmin:*:*:*:*:*:*:*:*
Vendors & Products Phpmyadmin
Phpmyadmin phpmyadmin
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 7.7, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-346

    Origin Validation Error

  • CWE-352

    Cross-Site Request Forgery (CSRF)

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 30, 2026, 4:06 PM
Reserved
Oct 30, 2026, 2:41 AM
Status
Analyzed
Published
Oct 30, 2026, 12:16 PM
Modified
Nov 3, 2026, 4:08 PM
Severity
Important
Public date
Oct 30, 2026, 11:30 AM