Loading vulnerability…
The Welcart e-Commerce WordPress plugin before version 2.8.5 contains a vulnerability where user input is not properly validated before being used to output the content of a file. This flaw allows an unauthenticated attacker to read arbitrary files from the server by crafting a malicious request.
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 is a small standalone Python proof-of-concept repository for CVE-2022-4140 affecting the WordPress usc-e-shop/Welcart e-Commerce plugin. The repository contains an MIT license, README usage documentation, one executable Python exploit (exploit.py), and a pinned requests dependency. The script accepts a WordPress base URL and optional target file path, fingerprints the installed plugin by requesting its public readme.txt, then requests content-log.php with an attacker-controlled logfile parameter. Successful exploitation returns the contents of the selected file, with /etc/passwd used as the default demonstration target. It provides no shell, command execution, persistence, or post-exploitation functionality. The version check can be bypassed with --disable-version-check, which is useful where the plugin readme is unavailable or version parsing fails.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.