dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-1311

HIGH · 8.8 CVSS v3.1 Published 2026-02-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 Worry Proof Backup plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 0.2.4 via the backup upload functionality. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload a malicious ZIP archive with path traversal sequences to write arbitrary files anywhere on the server, including executable PHP files. This can lead to remote code execution.

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 Worry Proof Backup WordPress plugin fails to properly sanitize path traversal sequences in uploaded ZIP archives during the backup restoration process. Authenticated users with Subscriber-level access can craft malicious ZIP files containing paths like ../../../webshell.php to write arbitrary executable files outside the intended upload directory, achieving remote code execution.

MitigationUpdate the plugin to the latest version which should contain proper path sanitization; if no patch is available, disable the plugin immediately and remove any suspicious files on the server.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify Worry Proof Backup plugin is installed
    Log in to WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'Worry Proof Backup' in the list. Note its current version number displayed below the plugin name.
    Affected if The plugin is present in the WordPress installation
  2. Check installed plugin version against affected range
    In the plugins list, locate the version number for Worry Proof Backup. Compare it to the affected versions: any version 0.2.4 or earlier is vulnerable.
    Affected if Version is 0.2.4 or lower
  3. Confirm backup upload functionality is enabled
    Navigate to the plugin settings page in WordPress admin (usually under Settings or Tools menu) and verify the backup upload/import feature is accessible. Check if there is an upload form for restoring backups.
    Affected if The backup upload/restore feature is present and accessible to users
  4. Identify accessible user roles for upload functionality
    In WordPress, go to Users > All Users and check the roles assigned. Verify if any users have Subscriber role or higher. The vulnerability allows any authenticated user with Subscriber-level access to exploit the flaw.
    Affected if There are active user accounts with Subscriber, Contributor, Author, or Editor roles who can access the site
  5. Inspect for unexpected files in writable directories
    Using file manager or SSH, check directories that would be writable via path traversal (typically wp-content/uploads/, wp-content/, or the web root) for any recently created .php files that were not intentionally uploaded through legitimate means.
    Affected if Unexpected PHP files exist in upload directories or web root that were not explicitly uploaded through known legitimate processes

You are affected if the Worry Proof Backup plugin version 0.2.4 or lower is installed, the backup upload feature is accessible, and user accounts with Subscriber-level access or higher exist on the 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 the plugin to the latest version which should contain proper path sanitization; if no patch is available, disable the plugin immediately and remove any suspicious files on the server.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version after 0.2.4)

  1. 1. Update the Worry Proof Backup plugin to the latest available version from the WordPress plugin repository.
  2. 2. Verify the update was applied successfully in the WordPress admin plugins list.
  3. 3. Confirm the installed version is newer than 0.2.4.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1311 — 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-1311 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