PHP Group up to 8.2.32/8.3.32/8.4.23/8.5.8 sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 2.17+ |
Summary
A vulnerability classified as critical has been found in PHP Group PHP up to 8.2.32/8.3.32/8.4.23/8.5.8. This impacts an unknown function. Performing a manipulation results in sql injection. This vulnerability is cataloged as CVE-2026-17543. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability, which was classified as critical, was found in PHP Group PHP up to 8.2.32/8.3.32/8.4.23/8.5.8. This affects some unknown processing. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-17543 since 07/27/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/30/2026). MITRE ATT&CK project uses the attack technique T1505 for this issue.
Upgrading to version 8.2.33, 8.3.33, 8.4.24 or 8.5.9 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-51090). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 8.2.0
- 8.2.1
- 8.2.2
- 8.2.3
- 8.2.4
- 8.2.5
- 8.2.6
- 8.2.7
- 8.2.8
- 8.2.9
- 8.2.10
- 8.2.11
- 8.2.12
- 8.2.13
- 8.2.14
- 8.2.15
- 8.2.16
- 8.2.17
- 8.2.18
- 8.2.19
- 8.2.20
- 8.2.21
- 8.2.22
- 8.2.23
- 8.2.24
- 8.2.25
- 8.2.26
- 8.2.27
- 8.2.28
- 8.2.29
- 8.2.30
- 8.2.31
- 8.2.32
- 8.3.0
- 8.3.1
- 8.3.2
- 8.3.3
- 8.3.4
- 8.3.5
- 8.3.6
- 8.3.7
- 8.3.8
- 8.3.9
- 8.3.10
- 8.3.11
- 8.3.12
- 8.3.13
- 8.3.14
- 8.3.15
- 8.3.16
- 8.3.17
- 8.3.18
- 8.3.19
- 8.3.20
- 8.3.21
- 8.3.22
- 8.3.23
- 8.3.24
- 8.3.25
- 8.3.26
- 8.3.27
- 8.3.28
- 8.3.29
- 8.3.30
- 8.3.31
- 8.3.32
- 8.4.0
- 8.4.1
- 8.4.2
- 8.4.3
- 8.4.4
- 8.4.5
- 8.4.6
- 8.4.7
- 8.4.8
- 8.4.9
- 8.4.10
- 8.4.11
- 8.4.12
- 8.4.13
- 8.4.14
- 8.4.15
- 8.4.16
- 8.4.17
- 8.4.18
- 8.4.19
- 8.4.20
- 8.4.21
- 8.4.22
- 8.4.23
- 8.5.0
- 8.5.1
- 8.5.2
- 8.5.3
- 8.5.4
- 8.5.5
- 8.5.6
- 8.5.7
- 8.5.8
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: PHP 8.2.33/8.3.33/8.4.24/8.5.9
Timeline
07/27/2026 CVE reserved07/30/2026 Advisory disclosed
07/30/2026 VulDB entry created
07/30/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2026-17543 (🔒)
GCVE (CVE): GCVE-0-2026-17543
GCVE (VulDB): GCVE-100-384789
EUVD: 🔒
Entry
Created: 07/30/2026 13:40Updated: 07/30/2026 14:09
Changes: 07/30/2026 13:40 (55), 07/30/2026 14:09 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.