dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-6227

HIGH · 7.2 CVSS v3.1 Published 2026-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The BackWPup WordPress plugin has a Local File Inclusion vulnerability in its REST API endpoint `/wp-json/backwpup/v1/getblock`. The `block_name` parameter uses non-recursive `str_replace()` to sanitize path traversal sequences, allowing `....//` to bypass the filter and include arbitrary PHP files. Attackers with Administrator-level access (or users granted backup permissions by admins) can read sensitive files like wp-config.php or achieve RCE.

MitigationUpdate BackWPup to the latest version beyond 5.6.6 and audit user permissions to ensure only trusted administrators have backup-related access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm BackWPup plugin is installed
    Go to WordPress admin dashboard > Plugins, or check the /wp-content/plugins/ directory for the backwpup folder
    Affected if The BackWPup plugin is present in the WordPress installation
  2. Identify the installed BackWPup version
    Check the plugin header in backwpup.php file or view the installed version in the WordPress Plugins admin page
    Affected if The installed version is 5.6.6 or lower, or cannot be determined to be newer than 5.6.6
  3. Verify the REST API endpoint is accessible
    Send a GET request to /wp-json/backwpup/v1/getblock?block_name=test and check for a valid response (authentication may be required)
    Affected if The endpoint responds (with or without authentication), indicating the vulnerable API is exposed
  4. Check for Administrator or backup-related user roles
    Review WordPress user roles under Users section, or check BackWPup plugin settings for any custom permission grants to lower-privileged users
    Affected if Any user has Administrator role, or any non-admin user has been granted backup task creation or management permissions
  5. Test path traversal filter bypass (optional verification)
    If authenticated as Admin, send a request to /wp-json/backwpup/v1/getblock?block_name=....//wp-config.php and check if the file content is returned
    Affected if The API returns content from wp-config.php or other arbitrary files, confirming the LFI vulnerability is exploitable

You are affected if BackWPup plugin is installed at version 5.6.6 or lower AND the REST API endpoint is accessible to your user account or any administrator on your site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update BackWPup to the latest version beyond 5.6.6 and audit user permissions to ensure only trusted administrators have backup-related access.

Recommended fix Moderate confidence

Latest BackWPup version (higher than 5.6.6)

  1. Check the current BackWPup plugin version installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate BackWPup and note the current version number
  4. Backup your WordPress site before performing any plugin updates
  5. Update BackWPup to the latest available version via Plugins > Installed Plugins > Update Now
  6. Verify the update was successful and the new version is installed
  7. Test that the REST endpoint /wp-json/backwpup/v1/getblock is no longer vulnerable by confirming path traversal sequences are properly blocked

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6227 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6227 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data