Loading vulnerability…
WPCargo Track & Trace for WordPress versions before 6.9.0 contains a file-write flaw that permits unauthenticated attackers to write a PHP file to an arbitrary location on the web server. An attacker can use the written PHP file to obtain remote code execution.
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 contains a Python exploit script (WpCargo.py) targeting CVE-2021-25003, an unauthenticated remote code execution vulnerability in the WPCargo WordPress plugin versions prior to 6.9.0. The exploit works by sending a specially crafted request to the vulnerable barcode.php endpoint, which results in a PHP webshell (<?=$_GET[1]($_POST[2]);?>) being written to the server as wp-content/wp-conf.php. The script then attempts to validate the shell by executing a command (cat /etc/passwd) and checking for the presence of 'root:x:0:0:root' in the response. The tool supports both single and multiple target modes, accepting either a single URL or a file containing a list of targets. The repository includes a README with usage instructions and a requirements.txt for dependencies. The main attack vector is network-based, exploiting a vulnerable HTTP endpoint to achieve remote code execution. The exploit is operational, providing a working webshell payload for post-exploitation activities.
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.
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.