Loading vulnerability…
CVE-2025-13597 is a critical vulnerability in the AI Feeds plugin for WordPress affecting all versions up to and including 1.0.11. The flaw is caused by a missing capability check in the plugin file 'actualizador_git.php'. Because access control is not properly enforced, an unauthenticated remote attacker can invoke functionality that downloads arbitrary GitHub repositories and writes their contents onto the target server, overwriting existing plugin files. This effectively creates an arbitrary file upload/overwrite condition within the plugin directory and may enable remote code execution if attacker-controlled PHP code is written to an executable 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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a Python exploit (CVE-2025-13597.py) and a detailed README for a critical unauthenticated arbitrary file upload vulnerability in the AI Feeds WordPress plugin (<= 1.0.11). The exploit leverages the actualizador_git.php endpoint, which allows unauthenticated users to download and extract arbitrary GitHub repositories into the plugin directory, overwriting files and enabling remote code execution. The provided exploit script automates uploading a malicious shell.php from a user-controlled GitHub repo and then interacts with the shell to execute arbitrary commands. The README provides technical analysis, PoC instructions, and a breakdown of the vulnerable PHP code. The main attack vector is network-based, targeting a specific HTTP endpoint on vulnerable WordPress installations. The exploit is operational, providing a working web shell payload for post-exploitation.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.