Loading vulnerability…
CVE-2025-23968 is an unrestricted file upload vulnerability in the WPCenter AiBud WP WordPress plugin. The issue allows upload of a file with a dangerous type, specifically enabling an attacker to upload a web shell to the web server. The vulnerability affects AiBud WP through version 1.8.5. Based on the available information, the flaw is consistent with insufficient validation or restriction of uploaded file types in the plugin's upload handling functionality.
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 contains a working exploit for CVE-2025-23968, a vulnerability in the AI Bud WordPress plugin (<= 1.8.5). The exploit leverages an insecure file renaming feature in the plugin's REST API endpoint `/wp-json/ai-buddy/v1/wp/attachments`, which allows an authenticated administrator to upload arbitrary files (including PHP web shells) to the WordPress uploads directory. The exploit is implemented in Python (`cve-2025-23968.py`) and automates the process of logging in as an administrator, extracting a required nonce, uploading a PHP shell, and executing a test command via the shell. The README.md provides detailed background, manual exploitation steps, and code snippets from the vulnerable plugin. The exploit requires valid admin credentials and targets WordPress sites with the vulnerable plugin installed. The main attack vector is network-based, exploiting the REST API endpoint to achieve remote code execution.
6 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.