dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-10307

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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 Backuply – Backup, Restore, Migrate and Clone plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete backup functionality in all versions up to, and including, 1.4.8. This makes it possible for authenticated attackers, with Administrator-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

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 Backuply WordPress plugin up to version 1.4.8 lacks proper path validation in its delete backup function, allowing authenticated administrators to delete arbitrary files on the server by manipulating file paths. Deletion of critical files like wp-config.php can trigger WordPress reinstallation, leading to potential site compromise and remote code execution.

MitigationUpdate the Backuply plugin to the latest version immediately. If immediate update is not possible, restrict administrator-level access and monitor server logs for suspicious file deletion activity.

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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 Backuply plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Backuply' in the list, or check the /wp-content/plugins/ directory for the backuply folder
    Affected if The Backuply plugin folder exists in the WordPress installation
  2. Check installed Backuply version
    In WordPress admin > Plugins > Installed Plugins, find Backuply and view the version number displayed beneath the plugin name, or inspect the main plugin file (e.g., backuply.php) for the 'Version' header comment
    Affected if The installed version is 1.4.8 or any earlier version
  3. Verify delete backup functionality exists
    In WordPress admin dashboard, locate the Backuply plugin menu and check if a delete backup or remove backup option is present in the backup management interface
    Affected if The plugin's backup deletion interface is accessible to administrator users
  4. Check for suspicious file deletion attempts in logs
    Review WordPress debug logs (wp-content/debug.log if enabled) and server access/error logs for unusual delete requests targeting files outside the expected backup directory, such as wp-config.php or other critical system files
    Affected if Log entries show deletion requests for files outside the typical backup storage path (e.g., /wp-content/backuply/ or similar)

A WordPress site is affected if the Backuply plugin version 1.4.8 or earlier is installed and the delete backup feature is accessible to authenticated administrators, enabling path traversal-based arbitrary file deletion.

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 Backuply plugin to the latest version immediately. If immediate update is not possible, restrict administrator-level access and monitor server logs for suspicious file deletion activity.

Recommended fix High confidence

1.5.0

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Backuply plugin in the list
  4. Click 'Update Now' if automatic update is available, or manually download version 1.5.0+ from wordpress.org/plugins/backuply and upload via Plugins > Add New > Upload Plugin
  5. Verify the update was successful by checking the installed version is 1.5.0 or higher

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-2025-10307 — 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-2025-10307 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