SPX (php-spx) through version 0.4.15 contains a directory traversal vulnerability in handling of SPX_UI_URI. The flaw allows arbitrary files to be read.
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 a Python 3 proof-of-concept exploit for CVE-2024-42007, a path traversal vulnerability in php-spx versions 0.4.15 and earlier. The exploit script (CVE_2024_42007.py) takes a target URL and an optional file path (defaulting to /etc/passwd), then crafts an HTTP GET request with a specially encoded SPX_UI_URI parameter to traverse directories and read arbitrary files from the server. The script checks for a detection string in the response to confirm successful exploitation. The repository consists of the exploit script and a README.md with usage instructions and a summary of the vulnerability. The exploit is unauthenticated and targets web servers running vulnerable versions of php-spx.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.