Loading vulnerability…
The SportsPress plugin for WordPress is vulnerable to Local File Inclusion (LFI) in all versions up to and including 2.7.26 via a shortcode attribute, template_name. Insufficient validation of the template name allows an authenticated attacker (contributor role or higher) to influence the file path that is included, enabling inclusion of arbitrary files from the server filesystem. Depending on what files can be included, this can lead to disclosure of sensitive information and, if attacker-controlled PHP can be placed on the server and then included, execution of arbitrary PHP code in the context of the WordPress/PHP process.
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.
Repository contains a single Python exploit script (CVE-2025-15368_Exploit.py) plus README and MIT license. The script targets SportsPress (WordPress plugin) versions <= 2.7.26 and implements an authenticated, network-based exploit. Core capabilities: - Authenticates to WordPress via /wp-login.php using provided credentials and maintains a session (requests.Session, SSL verification disabled). - LFI: abuses the SportsPress [event_list] shortcode by setting template_name to an attacker-controlled path (with traversal attempts) to include/read arbitrary local files. The tool automates nonce retrieval from wp-admin pages and attempts to render the shortcode (via post creation/preview flow) to capture included file contents. - RCE chain: per README and visible code structure, it automates uploading a malicious file (requires Author+), then uses the same LFI inclusion primitive to include the uploaded file and execute an attacker-supplied OS command (default: id), attempting to extract and print output from the HTTP response. Structure/purpose: - CVE-2025-15368_Exploit.py: CLI tool with two modes (--lfi and --rce). Includes helper methods for login, nonce scraping, LFI triggering, and chained exploitation (chain_lfi/chain_rce referenced in main). Uses regex to locate nonces and user_id in wp-admin HTML/JSON. - README.md: documents prerequisites, roles required (Contributor+ for LFI, Author+ for RCE), and example commands. No hardcoded external C2 infrastructure is present; all network interaction is with the target WordPress instance under the user-supplied base URL.
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.
4 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.