⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Critical · CVSS 9.8 ⚠ ACTIVELY EXPLOITED — CISA KEV

How to Fix CVE-2024-4577: Command Injection in PHP

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 9.8 - Critical
Actively exploited?Yes, listed in CISA KEV (added 2024-06-12)
Affected8.1.* < 8.1.29, 8.2.* < 8.2.20, 8.3.* < 8.3.8
Fixed inSee vendor advisory
Type (CWE)CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Patch immediately. CISA's KEV listing means active exploitation is confirmed. Federal agencies must remediate by 2024-07-03.

What is CVE-2024-4577?

CVE-2024-4577 is an OS command injection bug in PHP. The product builds a shell command from untrusted input without escaping, so injected metacharacters run as the service account, often root or SYSTEM. Vendor description: 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.

Why this CVE matters

Command injection in a network appliance or management console gives the attacker the same privileges as the service account, which is usually root or SYSTEM. From there, persistence, lateral movement, and credential theft follow with off-the-shelf tooling.

For deployments of PHP that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Confirmed in-the-wild exploitation makes that assumption mandatory, not cautious. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Run php -v to read the installed PHP version and confirm whether it is in the affected range.

How to fix CVE-2024-4577

  1. Read the vendor advisory in full: https://github.com/php/php-src/security/advisories/GHSA-3qgc-jrrr-25jv
  2. Upgrade PHP to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Rotate any credentials, API keys, or session tokens that the vulnerable service touched. An unauthenticated RCE-class flaw means anything the process could see should be treated as exposed.
  5. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  6. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Apply the Microsoft security update


# The exact KB number is listed in the Microsoft advisory: https://github.com/php/php-src/security/advisories/GHSA-3qgc-jrrr-25jv
# Confirm the patch is missing on this host
Get-Hotfix -Id <KB-from-advisory> -ErrorAction SilentlyContinue

# Install the rollup that ships the fix
Install-Module PSWindowsUpdate -Force -SkipPublisherCheck
Import-Module PSWindowsUpdate
Get-WindowsUpdate -KBArticleID <KB-from-advisory> -AcceptAll -Install -AutoReboot

# Verify the patch is now present
Get-Hotfix -Id <KB-from-advisory>


# Inventory missing patches across a Windows fleet via Ansible (winrm)
ansible windows -m win_updates -a "category_names=SecurityUpdates state=installed"

Verify the fix landed


# 1. Confirm the running version matches the fixed-in version from the advisory:
#    https://github.com/php/php-src/security/advisories/GHSA-3qgc-jrrr-25jv
#    Use the platform-specific version probe above.

# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
#    The scanner should no longer flag CVE-2024-4577 on the patched target.

# 3. Inspect recent service / kernel logs for crash loops or rollback events.
journalctl -u <service> --since "10 minutes ago"
dmesg --since "10 minutes ago"

If you cannot patch immediately

Restrict access to the management or affected endpoint at the network layer. If the vendor lists a configuration toggle that disables the vulnerable feature, use it until you can patch.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unexpected administrator accounts in PHP, scheduled tasks or cron jobs you did not create, new files in web-accessible directories, and outbound connections to addresses not in your baseline. Suspicious requests to the vulnerable endpoint immediately followed by successful 200-class responses with unusually large bodies are a strong indicator of exploitation. Because PHP sits on CISA's Known Exploited Vulnerabilities catalog for this CVE, defenders should also pull the IOC list from the vendor advisory and from CISA's analysis if one was published.

Frequently asked questions

Is CVE-2024-4577 being exploited in the wild?

Yes. CISA added CVE-2024-4577 to the Known Exploited Vulnerabilities catalog, which means active exploitation has been confirmed by federal observation or credible vendor reporting.

Will a WAF or IDS rule fully mitigate CVE-2024-4577?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Do I need to assume compromise if my PHP was internet-facing and unpatched?

For an unauthenticated RCE-class flaw exposed to the public internet during the known exploitation window, yes. Review logs, rotate credentials the process could access, and look for unexpected accounts, scheduled tasks, or outbound connections.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*