CVE-2024-8927VulnerabilityPublished 10 Oct 2024Updated 3 Nov 2025

CVE-2024-8927: PHP · Vulnerability

Affects PHPSource CVE Database V5

Not known to be exploited · CVSS 7.5 High · fixed in 8.3.12 : patch PHP soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 1.0% chance of exploitation in 30 days – higher than 64% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.3.12, 8.2.24, 8.1.30

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
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: 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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 10 Oct 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 2026-10-25.

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/php-src to 8.3.12, 8.2.24 or 8.1.30.

Affected software

Product	Affected	Fixed in
GitHubphp/php-src`pkg:github/php/php-src`Other threats	Affected >=8.1.0 <8.1.30 >=8.2.0 <8.2.24 >=8.3.0 <8.3.12	Fixed in 8.1.30 8.2.24 8.3.12

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

AI-suggested

1. 2. In the interim, review and harden the web server and PHP CGI configurations to ensure that cgi.force_redirect is enabled and properly enforced. 3. Implement strict input validation and sanitization on HTTP headers to reduce the risk of header manipulation. 4. Restrict direct access to the PHP CGI binary by configuring web server access controls and firewall rules. 5. Monitor web server logs for suspicious requests that attempt to manipulate HTTP_REDIRECT_STATUS or other environment variables. 6. Employ web application firewalls (WAFs) with rules designed to detect and block attempts to exploit this vulnerability. 7. Conduct regular vulnerability scanning and penetration testing focused on PHP CGI configurations. 8. Educate development and operations teams about secure PHP deployment practices, especially regarding CGI mode. 9. Isolate critical web applications and sensitive data to minimize exposure in case of exploitation. 10. Maintain an incident response plan to quickly address any exploitation attempts or breaches.

Description

In PHP versions 8.1.* before 8.1.30, 8.2.* before 8.2.24, 8.3.* before 8.3.12, HTTP_REDIRECT_STATUS variable is used to check whether or not CGI binary is being run by the HTTP server. However, in certain scenarios, the content of this variable can be controlled by the request submitter via HTTP headers, which can lead to cgi.force_redirect option not being correctly applied. In certain configurations this may lead to arbitrary file inclusion in PHP.

Impact

For European organizations, the impact of CVE-2024-8927 can be significant, especially for those running web applications on vulnerable PHP versions in CGI mode. Successful exploitation could allow attackers to include arbitrary files, potentially exposing sensitive configuration files, source code, or other protected data, leading to confidentiality breaches. This could result in data leaks, intellectual property theft, or exposure of credentials. While the vulnerability does not directly affect integrity or availability, the information disclosure could facilitate further attacks such as privilege escalation or remote code execution if combined with other vulnerabilities. Organizations in sectors such as finance, healthcare, government, and e-commerce, which often rely on PHP-based web applications, may face increased risk. The ease of remote exploitation without authentication means attackers can target vulnerable servers at scale, increasing the threat landscape. Additionally, compliance with GDPR and other data protection regulations could be impacted if sensitive personal data is exposed due to this vulnerability.

CWE-1220Insufficient Granularity of Access Control (opens in a new tab)
Base weakness
The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets.
Architecture and Design · Implementation · Testing
Access-control-policy protections must be reviewed for design inconsistency and common weaknesses.; Access-control-policy definition and programming flow must be tested in pre-silicon, post-silicon testing.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Exploiting Incorrectly Configured Access Control Security Levels (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:09 UTC

WeaknessesCWE-1220

Technical details

References

Community reviews

Related threats