CVE-2025-2249 affects the SoJ SoundSlides plugin for WordPress in all versions up to and including 1.2.2. The vulnerability is caused by missing file type validation in the soj_soundslides_options_subpanel() function, allowing authenticated users to upload arbitrary files to the server. According to the provided description, attackers with Contributor-level access or higher can exploit this weakness to place attacker-controlled files on the affected WordPress host. Because uploaded files may include executable server-side content, this can lead to remote code execution depending on server configuration and file handling behavior.
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 a fully functional exploit for CVE-2025-2249, targeting the WordPress SoJ SoundSlides plugin (versions <= 1.2.2). The main exploit script (CVE-2025-2249.py) is written in Python and automates the exploitation process. It first checks the plugin version by fetching the readme.txt file, then logs in to WordPress using provided credentials. The script generates a ZIP archive containing a PHP webshell and supporting files, uploads it via the plugin's vulnerable admin endpoint, and finally provides an interactive shell interface to execute arbitrary system commands on the compromised server. The exploit requires valid WordPress credentials (Contributor or higher). The repository includes a README with detailed usage instructions, a requirements.txt for dependencies, and a LICENSE file. The main attack vector is network-based, exploiting an authenticated arbitrary file upload vulnerability to achieve remote code execution via a web-accessible PHP shell.
2 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.