The Insert or Embed Articulate Content into WordPress plugin (up to version 4.3000000023) fails to properly restrict the file extensions that can be imported on the server. This allows attackers to upload zip files containing malicious code, potentially leading to remote code execution or other attacks depending on the server configuration and the nature of the uploaded files.
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 an operational exploit for CVE-2024-0757, targeting the 'Insert or Embed Articulate Content into WordPress' plugin (<= 4.3000000023). The exploit is implemented in Python (exploit.py) and automates the process of logging into a WordPress site, extracting necessary tokens (nonce and post ID), and uploading a ZIP file containing a shell via the vulnerable plugin's AJAX endpoint. Upon successful upload, the script outputs the URL to the uploaded shell, granting the attacker remote code execution capabilities. The repository includes a README with usage instructions and a requirements.txt for dependencies. The main attack vector is network-based, exploiting an insecure file upload vulnerability. Key endpoints include standard WordPress login and admin pages, as well as the plugin's AJAX upload handler. The exploit requires valid WordPress credentials and a vulnerable plugin version.
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.