Quick answers
- Is CVE-2026-119427 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119427 being exploited in the wild.
- How severe is CVE-2026-119427?
- Medium severity, with a CVSS score of 4.2, published 30 October 2026.
- Which products and versions are affected?
- phpMyAdmin through 5.2.3.
- Is there a fix for CVE-2026-119427?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-119427 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-119427?
- Check whether you run phpMyAdmin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The Designer component's saveSetting() function in phpMyAdmin 5.2.3 concatenates unescaped json_encode() output into a single-quoted SQL UPDATE/INSERT statement executed as the control user. An authenticated attacker can inject a single quote and SQL comment sequence in the value parameter to break the WHERE clause, allowing modification of arbitrary rows in pma__designer_settings table. The vulnerability exists because json_encode() does not escape single quotes, unlike the quoteString() method used in phpMyAdmin 6.x.
Affected products
- phpMyAdmin phpMyAdmin through 5.2.3
Timeline
- 2026-10-30: disclosed
- 2026-10-30: advisory