basicsecurity.net
Proof, not just disclosure.
Threats / PHP Group / CVE-2024-4577
CVE-2024-4577 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-123Ransomware use Flagged3EPSS 0.99987 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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
940 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.
CISA KEV ↗Confirmed
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
Affected: PHP Group, PHP. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-78 OS Command Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 940 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by php (CNA)
  • Named finder/reporter credit (CVE.org)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • Disclosure & credit2
    Catalogued by phpCNA