dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-13910

HIGH · 7.2 CVSS v3.1 Published 2025-03-01
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 Database Backup and check Tables Automated With Scheduler 2024 plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the 'database_backup_ajax_delete' function in all versions up to, and including, 2.35. 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). The vulnerability was partially patched in version 2.36.

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 Database Backup and check Tables Automated With Scheduler 2024 WordPress plugin has an arbitrary file deletion vulnerability in the 'database_backup_ajax_delete' function due to insufficient path validation. Authenticated administrators can delete arbitrary files on the server, including critical files like wp-config.php, leading to potential remote code execution through WordPress reinstallation.

MitigationUpdate to version 2.36 or later. Note that version 2.36 was only a partial patch—review the vendor's release notes for complete remediation and consider additional hardening such as restricting AJAX capabilities or implementing additional file access controls.

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. Verify the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Database Backup and check Tables Automated With Scheduler 2024' or check the plugin files in wp-content/plugins/ for a folder containing 'database-backup' or similar naming
    Affected if The plugin is not installed means not affected
  2. Determine the installed plugin version
    In WordPress admin Plugins page, click on the plugin name to view details and find the version number, or inspect the main plugin PHP file for a 'Version:' header comment
    Affected if Version is present and is below 2.36 (the patched version)
  3. Confirm the vulnerable AJAX endpoint exists
    Check if the file ajax_delete.php or similar exists in the plugin directory, or inspect the plugin code for the 'database_backup_ajax_delete' function handling file deletion
    Affected if The vulnerable function exists and is registered as a WordPress AJAX action
  4. Verify administrator access exists in WordPress
    Log into WordPress admin dashboard and confirm you have Administrator role privileges, or check Users > All Users for accounts with Administrator role
    Affected if At least one Administrator-level user account exists (this is required for exploitation)

You are affected if the plugin is installed with a version below 2.36 and the database_backup_ajax_delete function is accessible to administrator accounts in your WordPress installation.

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 to version 2.36 or later. Note that version 2.36 was only a partial patch—review the vendor's release notes for complete remediation and consider additional hardening such as restricting AJAX capabilities or implementing additional file access controls.

Recommended fix High confidence

Version 2.36 or later

  1. Log in to the WordPress admin dashboard with Administrator-level privileges
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Database Backup and check Tables Automated With Scheduler 2024' in the plugin list
  4. Check the current version number - if it is 2.35 or lower, the site is vulnerable
  5. Click 'Update now' if an update to version 2.36 or later is available
  6. After updating, verify the plugin is running version 2.36 or higher
  7. Note: The vendor description indicates version 2.36 includes a partial patch; monitor for subsequent updates that may fully address the path traversal vulnerability
Caveat WordPress plugin minor version updates typically do not introduce breaking changes; however, test the backup functionality after updating to ensure scheduled backups still operate correctly

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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