CVE-2026-17543
Analyzed Analyzed - Analysis Complete

Improper Input Validation in PHP Leading to SQL Injection

Vulnerability report for CVE-2026-17543, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-30

Last updated on: 2026-08-05

Assigner: PHP Group

Description

Improper escaping of backslashes in attacker-provided parameters would allow for trivial SQL injection in PHP versions from 8.2.* before 8.2.33, from 8.3.* before 8.3.33, from 8.4.* before 8.4.24, and from 8.5.* before 8.5.9.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-30
Last Modified
2026-08-05
Generated
2026-08-19
AI Q&A
2026-07-30
EPSS Evaluated
2026-08-18
NVD
EUVD

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
php php From 8.2.0 (inc) to 8.2.33 (exc)
php php From 8.3.0 (inc) to 8.3.33 (exc)
php php From 8.4.0 (inc) to 8.4.24 (exc)
php php From 8.5.0 (inc) to 8.5.9 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-17543 is a high-severity SQL injection vulnerability in PHP's ext-pgsql extension. It occurs in the php_pgsql_convert() function used by database operations like pg_insert() and pg_update(). The function fails to properly escape backslashes when PostgreSQL's standard_conforming_strings is enabled, allowing attackers to bypass input sanitization and inject malicious SQL code.

Detection Guidance

To detect this vulnerability, check if your PHP version is below 8.2.33, 8.3.33, 8.4.24, or 8.5.9. Use commands like 'php -v' to verify the version. Inspect applications using ext-pgsql functions such as pg_insert(), pg_update(), pg_select(), or pg_delete().

Review PostgreSQL logs for unusual queries or patterns indicating SQL injection attempts, such as backslash followed by single quotes.

Impact Analysis

This vulnerability allows attackers to execute arbitrary SQL commands on your database. If exploited, it could lead to unauthorized data access, modification, or deletion. Systems using PHP versions before 8.2.33, 8.3.33, 8.4.24, or 8.5.9 with the ext-pgsql extension and PostgreSQL are at risk.

Compliance Impact

This vulnerability could lead to data breaches, violating GDPR's data protection requirements and HIPAA's security rules for protected health information. Organizations may face fines, legal penalties, and reputational damage if exploited due to non-compliance with these regulations.

Mitigation Strategies

Upgrade PHP to the latest patched versions (8.2.33, 8.3.33, 8.4.24, or 8.5.9) immediately. Review and sanitize all inputs passed to PostgreSQL functions in your applications.

Disable PostgreSQL's standard_conforming_strings if not required, though upgrading PHP is the primary fix. Monitor for suspicious database activity.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-17543. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart