VulnerabilityPublished 13 Jul 2025Updated 4 Nov 2025

CVE-2025-1220: PHP · Server-Side Request Forgery (SSRF)

Affects PHPSource CVE Database V5

Not known to be exploited · CVSS 3.7 Low · fixed in 8.4.10 : update PHP when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

3.7Low

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

EPSS: 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.4.10, 8.3.23, 8.2.29 +1

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within 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 13 Jul 2025
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 the Debian debian/php package to 8.4.10, 8.3.23, 8.2.29 or 8.1.33.

Affected software

Product	Affected	Fixed in
Debiandebian/php`pkg:deb/debian/php`Other threats	Affected =8.1.0 <8.1.33 =8.2.0 <8.2.29 =8.3.0 <8.3.23 =8.4.0 <8.4.10	Fixed in 8.1.33 8.2.29 8.3.23 8.4.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, developers should implement strict input validation and sanitization to reject hostnames containing null characters or other suspicious input before passing them to network functions like fsockopen(). Additionally, security checks should be performed on the exact data used for network connections, avoiding discrepancies between validation and execution. Employing web application firewalls (WAFs) with rules to detect and block SSRF patterns can provide an additional layer of defense. Network segmentation and restricting outbound connections from web servers to only necessary destinations can limit the impact of potential SSRF exploitation. Regular code audits focusing on URL parsing and network request logic are recommended to identify similar inconsistencies. Monitoring logs for unusual outbound requests from web applications can help detect exploitation attempts early.

Description

In PHP versions:8.1.* before 8.1.33, 8.2.* before 8.2.29, 8.3.* before 8.3.23, 8.4.* before 8.4.10 some functions like fsockopen() lack validation that the hostname supplied does not contain null characters. This may lead to other functions like parse_url() treat the hostname in different way, thus opening way to security problems if the user code implements access checks before access using such functions.

Impact

For European organizations, this vulnerability poses a moderate risk primarily to web applications and services running on affected PHP versions. SSRF vulnerabilities can be leveraged to access internal network resources, potentially exposing sensitive data or enabling further lateral movement within corporate networks. Although the CVSS score is low, the impact depends heavily on the context of the vulnerable application, such as whether it processes untrusted user input in network-related functions. Organizations with PHP-based web infrastructure, especially those exposing internal APIs or services, could face risks of unauthorized internal resource access or information disclosure. Given the widespread use of PHP in Europe’s public and private sectors, including government portals, e-commerce, and financial services, the vulnerability could be exploited to bypass security controls if not mitigated. However, the high attack complexity and lack of known exploits reduce the immediate threat level. Still, failure to address this issue could lead to targeted SSRF attacks, particularly in environments where internal network segmentation or access controls are weak.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (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 10 Nov 2025, 20:24 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats