Wp_media BackWPup – WordPress Backup & Restore Plugin
BackWPup <= 5.6.6 - Authenticated (Administrator+) Local File Inclusion via 'block_name' Parameter
The BackWPup plugin for WordPress is vulnerable to Local File Inclusion via the `block_name` parameter of the `/wp-json/backwpup/v1/getblock` REST endpoint in all versions up to, and including, 5.6.6 due to a non-recursive `str_replace()` sanitization of path traversal sequences. This makes it possible for authenticated attackers, with Administrator-level access and above, to include arbitrary PHP files on the server via crafted traversal sequences (e.g., `....//`), which can be leveraged to read sensitive files such as `wp-config.php` or achieve remote code execution in certain configurations. Administrators have the ability to grant individual users permission to handle backups, which may then allow lower-level users to exploit this vulnerability.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- <= 5.6.6
Mitigation
The record names no fix. Check the vendor advisory below.
Timeline
Days relative to CVE publicationFirst public PoC 10 h before publication; not in CISA KEV. First PoC: Pixel-DefaultBR/CVE-2026-6227 (created 13 Apr 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| Pixel-DefaultBR/CVE-2026-6227 | 13 Apr 2026 −10 h | 0 | PoC via PoC Index |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.
PoC characteristics
What to hunt for in your logs · from 1 PoC repoPOST /wp-json/backwpup/v1/getblock
- Key headers
Cookie: wordpress_logged_in_{var}={var}X-Wp-Nonce: {var}- Body markers
block_name=....//....//....//....//wp-configblock_type=componentblock_data[type]=successblock_data[font]=smallblock_data[dismiss_icon]=trueblock_data[content]=You scheduled a new backup successfully!inapplication/x-www-form-urlencoded; charset=UTF-8- Seen in
- 1 repo: Pixel-DefaultBR/CVE-2026-6227
- Evidence
- Pixel-DefaultBR/CVE-2026-6227/README.md:57
Regex
Generated from PoC characteristics; not yet reviewed. Matches the request path and query.
(?i)^/wp-json/backwpup/v1/getblock(?:[?#].*)?$
Suricata
Template generated from PoC characteristics. Review before deploying.
alert http any any -> $HOME_NET any (msg:"GG PoC-Monitor CVE-2026-6227 wp_media BackWPup – WordPress Backup & Restore Plugin exploit attempt"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/wp-json/backwpup/v1/getblock"; http.header; content:"Cookie: wordpress_logged_in_"; nocase; http.header_names; content:"X-Wp-Nonce"; nocase; http.request_body; content:"block_name=....//....//....//....//wp-config"; http.request_body; content:"block_type=component"; http.request_body; content:"block_data[type]=success"; http.request_body; content:"block_data[font]=small"; http.request_body; content:"block_data[dismiss_icon]=true"; http.request_body; content:"block_data[content]=You scheduled a new backup successfully!"; reference:url,poc.griffinguard.io/cve/CVE-2026-6227; classtype:web-application-attack; sid:9663387; rev:1;)
Sigma
Template generated from PoC characteristics. Review before deploying.
title: wp_media BackWPup – WordPress Backup & Restore Plugin exploit attempt (CVE-2026-6227)
id: gg-pocmon-cve-2026-6227-9663387
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-6227. Generated, not reviewed.
references:
- https://poc.griffinguard.io/cve/CVE-2026-6227
logsource:
category: webserver
detection:
selection:
cs-method: POST
cs-uri-stem|contains|all:
- '/wp-json/backwpup/v1/getblock'
condition: selection
falsepositives:
- Authorized vulnerability scanning
level: high
tags:
- attack.initial_access
- attack.t1190
- cve.2026.6227