CVE-2024-5458VulnerabilityPublished 12 Jun 2024Updated 3 Nov 2025

CVE-2024-5458: PHP · CWE-345

Affects PHPSource CVE Database V5

Not known to be exploited · 12% EPSS · CVSS 5.3 Medium · fixed in 8.4.0 : update PHP when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 12.1% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.4.0, 8.3.0, 8.2.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade PHP to 8.4.0, 8.3.0 or 8.2.0.

Affected software

Product	Affected	Fixed in
PHP Group PHP	Affected >=8.1.0 <8.2.0 >=8.2.0 <8.3.0 >=8.3.0 <8.4.0	Fixed in 8.2.0 8.3.0 8.4.0

AI-suggested

1. Upgrade PHP to versions 8.1.29 or later, 8.2.20 or later, or 8.3.8 or later as soon as possible to incorporate the official fix. 2. Review all application code using filter_var with FILTER_VALIDATE_URL to identify reliance on user info components of URLs and implement additional validation or sanitization to reject malformed user info explicitly. 3. Implement strict input validation and sanitization at the application layer, especially for URLs accepted from untrusted sources, to prevent malformed URLs from entering business logic. 4. Use web application firewalls (WAFs) with custom rules to detect and block suspicious URL patterns that exploit this validation flaw. 5. Monitor application logs for unusual URL parsing errors or anomalies that could indicate exploitation attempts. 6. Educate developers about the limitations of built-in validation functions and encourage defense-in-depth strategies for input validation. 7. Conduct security testing and code audits focusing on URL handling and validation logic to identify and remediate similar issues proactively.

Description

In PHP versions 8.1.* before 8.1.29, 8.2.* before 8.2.20, 8.3.* before 8.3.8, due to a code logic error, filtering functions such as filter_var when validating URLs (FILTER_VALIDATE_URL) for certain types of URLs the function will result in invalid user information (username + password part of URLs) being treated as valid user information. This may lead to the downstream code accepting invalid URLs as valid and parsing them incorrectly.

Impact

For European organizations, this vulnerability poses a risk primarily to web applications and services relying on PHP versions 8.1, 8.2, or 8.3 for URL validation. Since PHP is widely used across Europe for web development, especially in CMS platforms, e-commerce, and custom web apps, the incorrect validation of URLs can lead to logic errors, potentially allowing attackers to bypass security controls that depend on URL validation. This could facilitate phishing, session hijacking, or injection of malicious URLs into application workflows. Although the vulnerability does not directly compromise confidentiality or availability, the integrity impact can lead to trust issues in URL handling, possibly enabling further chained attacks. European organizations in finance, government, healthcare, and e-commerce sectors are particularly sensitive to such integrity issues due to regulatory compliance and the critical nature of their web services. Failure to patch could expose these organizations to targeted attacks exploiting malformed URLs to manipulate application behavior or bypass security filters.

CWE-345Insufficient Verification of Data Authenticity (opens in a new tab)
Class weaknessOWASP Top 10 A08:2025: Software or Data Integrity Failures (opens in a new tab)
The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
XML Security (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
REST Assessment (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.2 (opens in a new tab)
V3.5.3 (opens in a new tab)
V13.2.6 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cache Poisoning (opens in a new tab)
DNS Cache Poisoning (opens in a new tab)
Spoofing of UDDI/ebXML Messages (opens in a new tab)
Application API Message Manipulation via Man-in-the-Middle (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2025, 23:15 UTC

WeaknessesCWE-345

Technical details

References

Community reviews

Related threats