Loading vulnerability…
The Migration, Backup, Staging – WPvivid Backup & Migration plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'upload_files' function in all versions up to, and including, 0.9.112. This makes it possible for authenticated attackers, with Administrator-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible. NOTE: Uploaded files are only accessible on WordPress instances running on the NGINX web server as the existing .htaccess within the target file upload folder prevents access on Apache servers.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept exploit for CVE-2024-13869, targeting the WPvivid Backup plugin for WordPress (versions <= 0.9.112). The exploit is implemented in a single Python script (CVE-2024-13869.py) and requires valid administrator credentials for the target WordPress instance. The script automates the process of logging in, extracting a required nonce, and uploading a PHP web shell (hack.php) via the vulnerable 'wpvivid_upload_files' action exposed by the plugin. Once uploaded, the shell can be accessed at '/wp-content/wpvividbackups/hack.php' and allows arbitrary command execution via the 'cmd' GET parameter. The README.md provides detailed usage instructions, manual exploitation steps, and technical details about the vulnerability. The repository is structured simply, with the main exploit script, a README, and a license file. No framework is used; the exploit is standalone.
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 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.