Quick answers
- Is CVE-2026-17543 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-17543 being exploited in the wild.
- How severe is CVE-2026-17543?
- Informational severity, with a CVSS score of 8.1, published 30 July 2026.
- Which products and versions are affected?
- PHP Group PHP 8.2.* before 8.2.33, 8.3.* before 8.3.33, 8.4.* before 8.4.24, 8.5.* before 8.5.9.
- Is there a fix for CVE-2026-17543?
- A patch was published on 2026-07-30. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-17543 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-17543?
- Check whether you run PHP Group PHP 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
A SQL injection vulnerability exists in the php_pgsql_convert() function within PHP's ext-pgsql extension. The root cause is the use of PQescapeStringConn() followed by wrapping the result in an escape string constant (E'...') via php_pgsql_add_quotes(). When PostgreSQL is configured with standard_conforming_strings = on (the default), PQescapeStringConn() does not escape backslashes. An attacker can provide a backslash followed by a single quote; the quote is doubled by the escaper, but the backslash then escapes the first of the doubled quotes, allowing the second quote to terminate the string and inject arbitrary SQL commands. This affects pg_insert(), pg_update(), pg_select(), and pg_delete(). The issue is resolved in PHP versions 8.2.33, 8.3.33, 8.4.24, and 8.5.9 by using non-escaping string constants instead.
Affected products
- PHP Group PHP 8.2.* before 8.2.33, 8.3.* before 8.3.33, 8.4.* before 8.4.24, 8.5.* before 8.5.9
Timeline
- 2026-07-30: disclosed
- 2026-07-30: advisory
- 2026-07-30: patched