Threats / PHP Group / CVE-2024-4577
CVE-2024-4577
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
PHP Group vulnerability
PHP on Windows in CGI mode contains an OS command injection vulnerability allowing arbitrary code execution. This is a bypass of CVE-2012-1823 protections.
Verdict
Today item, not a backlog item.
A critical command injection flaw in Windows PHP CGI deployments enables unauthenticated remote code execution. Active exploitation and ransomware deployment confirm severe real-world risk. Immediate patching required.
CISA KEV Yes · 2024-06-125Ransomware use Flagged5EPSS 0.99987 (verify live)6Exploit Weaponized · public PoC7CVSS 9.83CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
1001 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-06-12), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99987 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: PHP Group, PHP. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-78 OS Command Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 3 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft malicious input to PHP CGI parameters that bypass existing sanitization, injecting arbitrary OS commands.
Business
Attackers gain code execution with web server privileges, enabling data theft, system compromise, and lateral movement.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute reconnaissance commands to map the target environment, identify sensitive data, and locate backup systems.
Business
Threat actors establish persistence and identify high-value assets for encryption or exfiltration.
3
Lateral reach — past segmentation narrative 3
Attacker
I deploy ransomware payloads or data exfiltration tools across the compromised infrastructure.
Business
Organizations face operational shutdown, data loss, regulatory fines, and ransom demands with no guarantee of recovery.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by phpCNA
Credited with finding itOrange Tsai, DEVCORE Research Teamreporter