CVE-2025-10307 affects the Backuply – Backup, Restore, Migrate and Clone plugin for WordPress. In all versions up to and including 1.4.8, the plugin's delete backup functionality does not sufficiently validate file paths, allowing an authenticated attacker with Administrator-level privileges or higher to cause deletion of arbitrary files on the underlying server. The issue is effectively a path validation/path traversal weakness in a file-operation feature, where attacker-controlled path input can be used to target files outside the intended backup scope. Deleting security-critical application files, such as wp-config.php, can destabilize the site and create conditions that may be leveraged for remote code execution.
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.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.