Loading vulnerability…
CVE-2025-28915 is an unrestricted file upload vulnerability in the Theme Egg ThemeEgg ToolKit WordPress plugin (themeegg-toolkit). The provided description states that the flaw allows upload of a dangerous file type, specifically enabling an attacker to upload a web shell to the web server. The issue affects ThemeEgg ToolKit versions through and including 1.2.9. Based on the available information, the vulnerability stems from insufficient validation or restriction of uploaded file types, permitting server-executable content to be stored in a web-accessible location.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a Python exploit script (CVE-2025-28915.py) and a README.md. The exploit targets a file upload vulnerability in the ThemeEgg ToolKit WordPress plugin (version 1.2.9 and earlier), identified as CVE-2025-28915. The script automates the process of logging into a WordPress site, extracting a security nonce, and uploading a PHP web shell via a vulnerable AJAX endpoint. If successful, the shell is accessible under the uploads directory, allowing remote command execution. The README provides background, setup instructions, and usage examples. The exploit requires valid WordPress credentials and network access to the target. The main attack vector is network-based, exploiting HTTP endpoints specific to WordPress and the vulnerable plugin.
This repository contains a Python exploit script (CVE-2025-28915.py) targeting an authenticated arbitrary file upload vulnerability (CVE-2025-28915) in the ThemeEgg ToolKit WordPress plugin (versions <= 1.2.9). The exploit automates the following steps: (1) checks the plugin version by fetching its readme.txt, (2) logs in to WordPress using provided credentials, (3) extracts a security nonce from the plugin's admin page, (4) uploads a PHP web shell via the vulnerable admin-ajax.php endpoint, and (5) provides the likely URL of the uploaded shell for remote command execution. The payload is a simple PHP web shell that executes system commands via the 'cmd' GET parameter. The repository includes a README with usage instructions and a LICENSE file. The main attack vector is network-based, requiring valid WordPress credentials. The exploit is operational and can result in full server compromise if successful.
3 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.