Loading vulnerability…
CVE-2024-1874 is an OS command injection vulnerability in PHP on Windows when proc_open() is invoked using array command syntax. In PHP versions before 8.1.28, 8.2.18, and 8.3.5 in their respective release branches, insufficient escaping of command arguments can allow attacker-controlled arguments to be interpreted by the Windows shell as additional commands.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides proof-of-concept exploits for CVE-2024-1874, a command injection vulnerability in PHP's proc_open() function when used with array syntax and insufficient escaping. The vulnerability affects PHP versions 8.1.* before 8.1.29, 8.2.* before 8.2.20, and 8.3.* before 8.3.8, specifically on Windows platforms. The repository contains two main exploit files: 'index.php', which demonstrates the vulnerable code, and 'main.py', which acts as an exploit script by sending a crafted payload to a target PHP endpoint. The Python script targets a web-accessible PHP file and attempts to inject a command via a GET parameter, verifying success by checking for a specific string in the response. The exploit demonstrates the ability to execute arbitrary commands on the target system if it is running a vulnerable PHP version and exposes a suitable endpoint. No weaponized or framework-based code is present; this is a clear proof-of-concept repository.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.