# CVE-2026-6227: BackWPup <= 5.6.6 - Authenticated (Administrator+) Local File Inclusion via 'block_name' Parameter

> Authenticated administrators can exploit path traversal in BackWPup to read sensitive files or execute code via the block_name parameter.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-6gj4-hcqg-pjc8

## What is CVE-2026-6227?

CVE-2026-6227 is a high-severity path traversal vulnerability in wp_media BackWPup – WordPress Backup & Restore Plugin, published on 14 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-6227?


## How do I fix CVE-2026-6227?

No fix has been published for CVE-2026-6227 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6227 being exploited?

There is no known exploitation of CVE-2026-6227 in the wild and no public exploit code.

Public exploit code:

- https://github.com/Pixel-DefaultBR/CVE-2026-6227 (github_poc): https://github.com/Pixel-DefaultBR/CVE-2026-6227

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6227 and fix it if it is affected.

What it is: CVE-2026-6227 is a high-severity path traversal vulnerability in wp_media BackWPup – WordPress Backup & Restore Plugin, published on 14 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6227 in the wild and no public exploit code.

Affected product: wp_media BackWPup – WordPress Backup & Restore Plugin. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6227/ (Markdown: https://insights.sbomify.com/CVE-2026-6227/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6227
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6227
- OSV: https://osv.dev/vulnerability/CVE-2026-6227

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6227/
Summaries are generated and may contain mistakes; the official description above is the record.