dbcve.org
Wp Database BackupWordPress extension · Wpseeds

CVE-2016-10874

HIGH · 8.8 CVSS v3.1 Published 2019-08-12
Fix available
A fix is available. Upgrade to 4.3.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 before 4.3.3 for WordPress has CSRF.

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 4.3.3 contains a Cross-Site Request Forgery (CSRF) vulnerability. This allows attackers to trick authenticated administrators into performing unintended actions such as triggering database backup operations or modifying plugin settings through maliciously crafted requests.

MitigationUpdate the wp-database-backup plugin to version 4.3.3 or later to resolve the CSRF vulnerability.

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:< 4.3.3

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Locate the wp-database-backup plugin installation
    Navigate to wp-content/plugins/ in your WordPress installation directory and look for a folder named 'wp-database-backup' or similar (may also be 'wp-db-backup' or contain 'wpseeds').
    Affected if The plugin folder is not present means the plugin is not installed and therefore not affected.
  2. Identify the installed version number
    Open the main plugin PHP file (usually named similarly to the folder or 'wp-database-backup.php') and locate the version comment at the top of the file, typically in a format like 'Version: X.X.X' or within the plugin header comments.
    Affected if The version displayed is less than 4.3.3.
  3. Check via WordPress admin dashboard
    Log in to WordPress admin, go to Plugins > Installed Plugins, find the wp-database-backup plugin, and note the version number displayed under the plugin name.
    Affected if The version shown is below 4.3.3.
  4. Verify plugin is active
    In WordPress admin under Plugins > Installed Plugins, confirm whether the wp-database-backup plugin is currently activated.
    Affected if The plugin is active AND the version is below 4.3.3 - the CSRF vulnerability can be exploited.

You are affected if the wp-database-backup plugin by Wpseeds is installed, active, and running on a version lower than 4.3.3.

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.

From vendor data
Upgrade available Upgrade to 4.3.3 or later
Fixed in 4.3.3
Interim mitigation

Update the wp-database-backup plugin to version 4.3.3 or later to resolve the CSRF vulnerability.

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-2016-10874 — 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-2016-10874 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