What is CVE-2024-4577?

CVE-2024-4577 is Argument Injection in PHP-CGI. The supplied enrichment data classifies it as Remote Code Exec mapped to CWE-78 OS Command Injection.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

246 public PoC repositories reported; 2 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2024-4577 using CVSS 9.8, EPSS 100%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: Kimsuky (), MuddyWater (), RAZOR TIGER (), UAC-0020 (), Lazarus Group (), Ransomware use: Known. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVRansomwarecriticalRemote Code Execpublic exploit

CVE-2024-4577

CVE-2024-4577 — Argument Injection in PHP-CGI

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2024-4577 in CISA KEV with required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

In PHP versions 8.1.* before 8.1.29, 8.2.* before 8.2.20, 8.3.* before 8.3.8, when using Apache and PHP-CGI on Windows, if the system is set up to use certain code pages, Windows may use "Best-Fit" behavior to replace characters in command line given to Win32 API functions. PHP CGI module may misinterpret those characters as PHP options, which may allow a malicious user to pass options to PHP binary being run, and thus reveal the source code of scripts, run arbitrary PHP code on the server, etc.

Published Jun 9, 2024Updated Jun 17, 2026Sources: NVD, PHP Group (CNA), CISA, FIRST EPSS, GitHub, Exploit-DB, Red Hat (VEX), SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Jun 12, 2024

EPSS

100%

top of FIRST's scoreset

Affects

PHP Group

3 products listed

CVSS base

9.8

critical

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade PHP to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Federal deadline Jul 3, 2024 — passed 800 days ago

Red Hat VEX · CVE-2024-4577

fixed0affected0not affected299

workaround: Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applic…

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
PHP Group	PHP	8.1.* to < 8.1.29	Vulnerable
PHP Group	PHP	8.2.* to < 8.2.20	Vulnerable
PHP Group	PHP	8.3.* to < 8.3.8	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.8	CVSS 3.1	critical	3.9	5.9	php.net (CNA), NVD, PHP Group (CNA), Red Hat (VEX)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Execute Unauthorized Code or Commands
DoS: Crash, Exit, or Restart
Read Files or Directories
Modify Files or Directories

Mitigation: If at all possible, use library calls rather than external processes to recreate the desired functionality.

Weakness & attack patterns

CWE-78OS Command Injection

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-15 · Command DelimitersCAPEC-88 · OS Command InjectionCAPEC-43 · Exploiting Multiple Input Interpretation LayersCAPEC-108 · Command Line Execution through SQL InjectionCAPEC-6 · Argument Injection

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Jun 12, 2024

Federal deadline

Jul 3, 2024

passed 800 days ago

Ransomware use

Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

208

2 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Malware

Families a CTI source ties to this CVE. One named, with the total it tracks.

Families tracked

Named

Akira

akira, elf.akira, win.akira

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

14 more posts on this CVEShowing 5 of 19 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable PHP.
Monitor for scanner or exploit-pattern traffic after 246 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

KimsukyMuddyWaterRAZOR TIGERUAC-0020Lazarus Group

24 more threat groups on this CVEShowing 5 of 29 · Attribution, campaigns and the malware each one runsUnlock free

ip123.49.56.5478
AbuseIPDB Hourly Update · Aug 24, 2026
ip123.30.50.14860
Maltiverse IP List · Nov 23, 2024
ip192.210.186.20648
AbuseIPDB Hourly Update · Nov 28, 2025
ip45.164.39.25329
Zonefiles · Jan 8, 2021
ip195.177.94.8080
SOCRadar Threat Exchange Services · Jul 29, 2026

5 more indicators on this CVEShowing 5 of 10 · Hashes, addresses and domains from a live threat exchangeUnlock free

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Cve is exploited DuyDuongDuyDuong/CVE-2024-4577-Exploitation-AsyncRAT-Deployment-DFIR-Investigatio
Aug 14, 2026 · SOCRadar CTI
Added · CVSS 3.1 9.8 (AV:N)
Jun 17, 2026 · NVD
Cve is exploited gl1tch0x1/PHP_8.1.x_Exploit
Apr 30, 2026 · SOCRadar CTI
2025
Added · webapps entry: PHP CGI Module 8.3.4 - Remote Code Execution (RCE)
Jun 15, 2025 · Exploit-DB
2024
Added to CISA KEV catalog
Jun 12, 2024 · CISA
Initial · CVE published
Jun 9, 2024 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

17×SVRS was changedMar 31, 2026 – Jul 24, 2026 · SOCRadar CTI
7×TweetsMar 10, 2026 – Aug 3, 2026 · SOCRadar CTI
5×Github ReposApr 29, 2026 – Aug 10, 2026 · SOCRadar CTI

References

32 on the record

www.openwall.com/lists/oss-security/2024/06/07/1
Mailing List, Third Party Advisory, NIST
arstechnica.com/security/2024/06/php-vulnerability-allows-attackers-to-run-malicious-code-on-windows-servers/
Exploit, Press/Media Coverage, Third Party Advisory, GITHUB, NIST
blog.orange.tw/2024/06/cve-2024-4577-yet-another-php-rce.html
Third Party Advisory, NIST
cert.be/en/advisory/warning-php-remote-code-execution-patch-immediately
Third Party Advisory, GITHUB, NIST
devco.re/blog/2024/06/06/security-alert-cve-2024-4577-php-cgi-argument-injection-vulnerability-en/
Exploit, Third Party Advisory, NIST
github.com/11whoami99/CVE-2024-4577
Exploit, GITHUB, NIST
github.com/php/php-src/security/advisories/GHSA-3qgc-jrrr-25jv
Exploit, Third Party Advisory, GITHUB, NIST
github.com/rapid7/metasploit-framework/pull/19247
Exploit, Issue Tracking, Patch, NIST

Coverage

11 stories from the feeds we poll

6 more reports on this CVEShowing 5 of 11 · Vendor research and security press coverageUnlock free

Elsewhere on this site

PHP Groupevery CVE for this vendor
June 2024what else CISA listed
Remote Code Execsame class
CWE-78other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

Only the 5 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2024-4577 is Argument Injection in PHP-CGI, a critical vulnerability affecting PHP from PHP Group. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 246 public PoC repositories reported; 2 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 100% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.