Loading vulnerability…
CVE-2025-13595 is a critical vulnerability in the CIBELES AI plugin for WordPress affecting all versions up to and including 1.10.8. The flaw is caused by a missing capability check in the plugin file 'actualizador_git.php'. Because access to this functionality is not properly restricted, an unauthenticated remote attacker can invoke it to download arbitrary GitHub repositories to the target server and overwrite plugin files within the WordPress installation. By replacing plugin code with attacker-controlled content, the issue can lead to remote code execution on the affected site.
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-13595.py) and a detailed README for CVE-2025-13595, a critical unauthenticated arbitrary file upload vulnerability in the Cibeles AI WordPress plugin (versions <= 1.10.8). The exploit leverages the actualizador_git.php file, which allows unauthenticated users to download and extract arbitrary GitHub repositories into the plugin directory, overwriting files and enabling remote code execution. The provided Python script automates the attack: it sends a crafted HTTP GET request to actualizador_git.php with attacker-controlled parameters (owner, repo, token), causing the target to download a malicious repository containing a PHP web shell (shell.php). The script then accesses shell.php with a command parameter, confirming remote code execution. The README provides technical analysis, PoC steps, and explains the vulnerability in detail. The main endpoints involved are the vulnerable actualizador_git.php (for file upload) and the resulting shell.php (for command execution). The exploit is operational, requiring a GitHub repo with a shell and a valid token, and results in a persistent web shell on the target.
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.