Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.99% for the current model date.
BlackTreeCVE IntelligencePHP Group · PHP
Official source article: GitHub GHSA-HRWM-9436-5MV3 ↗. Check the applicable product and release in the original source.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · community | php83 | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 8.3.23-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.23v3.23 · community | php84 | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 8.4.9-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | php82 | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 8.2.29-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | php83 | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 8.3.23-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | php84 | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 8.4.10-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Debian trixietrixie · source | php8.4 | Vendor fix publishedDebian records a fixed source-package version for this release. | 8.4.10-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | php8.2 | Vendor fix publishedDebian records a fixed source-package version for this release. | 8.2.29-1~deb12u1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | php8.4 | Vendor fix publishedDebian records a fixed source-package version for this release. | 8.4.10-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | php8.4 | Vendor fix publishedDebian records a fixed source-package version for this release. | 8.4.10-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | php8.3 | Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree. | 8.3.6-0ubuntu0.24.04.5 | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Fix not verifiedIn PHP versions:8.1.* before 8.1.33, 8.2.* before 8.2.29, 8.3.* before 8.3.23, 8.4.* pgsql and pdo_pgsql escaping functions do not check if the underlying quoting functions returned errors. This could cause crashes if Postgres server rejects the string as invalid.
In PHP versions:8.1.* before 8.1.33, 8.2.* before 8.2.29, 8.3.* before 8.3.23, 8.4.* pgsql and pdo_pgsql escaping functions do not check if the underlying quoting functions returned errors. This could cause crashes if Postgres server rejects the string as invalid.
Attacker-controlled data is not kept separate from SQL query syntax, allowing the intended database operation to be changed.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
In PHP versions:8.1.* before 8.1.33, 8.2.* before 8.2.29, 8.3.* before 8.3.23, 8.4.* pgsql and pdo_pgsql escaping functions do not check if the underlying quoting functions returned errors. This could cause crashes if Postgres server rejects the string as invalid.
Attacker-controlled data is not kept separate from SQL query syntax, allowing the intended database operation to be changed.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'). 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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 13 Jul 2025 · Last source change 4 Nov 2025, 21:09 UTC · CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Core structured fields are present and their contributing authorities are shown above.
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.