dbcve.org
Wp Database BackupWordPress extension · Wpseeds

CVE-2019-25224

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-25
Fix available
A fix is available. Upgrade to 5.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 WP Database Backup plugin for WordPress is vulnerable to OS Command Injection in versions before 5.2 via the mysqldump function. This vulnerability allows unauthenticated attackers to execute arbitrary commands on the host operating system.

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 WP Database Backup plugin for WordPress versions before 5.2 contains an OS command injection vulnerability in the mysqldump function, allowing unauthenticated attackers to execute arbitrary commands on the host operating system with the privileges of the web server.

MitigationUpgrade the WP Database Backup plugin to version 5.2 or later to patch the command injection vulnerability. Consider restricting web server permissions as a defense-in-depth measure.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Database BackupWordPress extension
Affected:< 5.2

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Check if WP Database Backup plugin is installed
    In WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'WP Database Backup' or 'Wpseeds WP Database Backup'. Alternatively, check the plugin directory wp-content/plugins/ for a folder named 'wp-database-backup' or similar.
    Affected if Plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find WP Database Backup, and read the version number displayed beneath the plugin name. Alternatively, check the main plugin PHP file for a 'Version:' header comment.
    Affected if Version number is less than 5.2 (for example, 5.1, 5.0, 4.x, etc.)
  3. Verify the mysqldump functionality is accessible
    Check if the database backup feature can be accessed. Look for backup-related AJAX endpoints or admin pages that trigger the mysqldump function. Inspect plugin PHP files for calls to exec(), shell_exec(), or mysqldump commands.
    Affected if The mysqldump backup function is present and executable within the plugin
  4. Check for signs of command injection exploitation
    Review web server access logs and error logs for suspicious patterns involving mysqldump commands with unexpected parameters, shell metacharacters, or base64-encoded payloads. Look for POST requests to backup-related endpoints with unusual command strings.
    Affected if Logs show mysqldump commands containing shell metacharacters (such as ;, |, &&, $(), or backticks) that were not initiated by legitimate admin actions

User is affected if the WP Database Backup plugin version is below 5.2 and the mysqldump function is accessible, or if logs show evidence of exploitation attempts against this vulnerability.

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
Upgrade available Upgrade to 5.2 or later
Fixed in 5.2
Vendor patch plugins.trac.wordpress.org →
Interim mitigation

Upgrade the WP Database Backup plugin to version 5.2 or later to patch the command injection vulnerability. Consider restricting web server permissions as a defense-in-depth measure.

Recommended fix High confidence

WP Database Backup version 5.2 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'WP Database Backup' plugin
  4. Click 'Update now' if an update is available, or manually upload version 5.2 or later
  5. Verify the plugin version is 5.2 or higher after update
  6. Check plugin for any signs of malicious modification

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

Fix this in Wp Database Backup Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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