Loading vulnerability…
CVE-2024-43160 is an Unrestricted Upload of File with Dangerous Type vulnerability in BerqWP, affecting versions up to and including 1.7.6. The vulnerability allows attackers to upload files of dangerous types, such as scripts or executables, which can then be executed on the server, leading to code injection.
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 (BerqWP.py) and a README.md. The exploit targets CVE-2024-43160, a vulnerability in the BerqWP WordPress plugin (versions <= 1.7.6) that allows unauthenticated arbitrary file upload due to missing file type validation. The script is designed for mass exploitation: it takes a list of target URLs and uses multithreading to scan each for the vulnerable plugin by checking for a specific readme file. If the plugin is detected and is a vulnerable version, the script attempts to upload a base64-encoded PHP webshell via the 'wp-json/optifer/v1/store-webp' endpoint. If successful, the shell is accessible at a random .php filename on the target server, and its URL is saved to a file. The payload is a simple PHP webshell that allows further file uploads and code execution. The README provides usage instructions and context about the vulnerability. No hardcoded IPs or domains are present; all endpoints are relative to the target URLs provided by the user.
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.