Loading vulnerability…
CVE-2026-6227 is a local file inclusion vulnerability in the BackWPup plugin for WordPress affecting all versions up to and including 5.6.6. The flaw exists in the /wp-json/backwpup/v1/getblock REST endpoint, where the block_name parameter is insufficiently sanitized. Specifically, path traversal sequences are filtered using a non-recursive str_replace() approach, which can be bypassed with crafted input such as ....//. An authenticated attacker with Administrator-level access, or another user delegated backup-handling permissions by an administrator, can exploit this weakness to traverse directories and include arbitrary PHP files present on the server. Depending on the target file and server configuration, exploitation can expose sensitive data such as credentials in wp-config.php and may lead to remote code execution in certain environments.
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.
wp-config.php. In certain configurations, inclusion of attacker-influenced or otherwise dangerous PHP files may also enable remote code execution. The issue therefore impacts confidentiality and, in some cases, integrity and availability of the affected WordPress instance and potentially the underlying host environment.If you can’t patch tonight, do this now.
/wp-json/backwpup/v1/getblock endpoint via web server or WAF rules. Monitor for suspicious requests containing traversal patterns such as ....// targeting the block_name parameter, and review logs for unauthorized access to sensitive files.Patch, then assume compromise.
block_name parameter in the /wp-json/backwpup/v1/getblock endpoint should be corrected by implementing robust canonicalization and strict allowlisting of permitted block names or file paths, rather than relying on non-recursive string replacement of traversal tokens. Access to backup-related functionality should also be reviewed to ensure only fully trusted users retain those permissions.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.
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.
2 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.