Wp Database BackupWordPress extension · Wpseeds
CVE-2016-10876
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 · uneditedThe wp-database-backup plugin before 4.3.1 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 confidenceThe wp-database-backup plugin for WordPress versions before 4.3.1 contains a Cross-Site Request Forgery (CSRF) vulnerability. This allows attackers to trick authenticated administrators into performing unintended database backup actions, such as creating or deleting backups, by tricking them into visiting malicious pages while logged in.
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
< 4.3.1CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Verify wp-database-backup plugin is installedAccess WordPress admin dashboard and navigate to Plugins > Installed Plugins, or inspect the wp-content/plugins directory for a folder containing 'wp-database-backup' or similar namingAffected if The plugin is present in the plugins directory or listed in WordPress admin
-
Check if the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify the wp-database-backup plugin status shows as 'Active'Affected if The plugin is activated on the WordPress site
-
Determine installed plugin versionIn WordPress admin Plugins list, click on the plugin to view details and locate the version number, or open the main plugin PHP file (typically in wp-content/plugins/wp-database-backup/ or similar) and check the plugin header comment for 'Version' fieldAffected if The version displayed is lower than 4.3.1 (for example: 4.3.0, 4.2.x, etc.)
-
Confirm version is within affected rangeCompare the identified version against the affected range: versions below 4.3.1 are vulnerable; version 4.3.1 and later include the fixAffected if Installed version is less than 4.3.1 AND the plugin is active with an authenticated administrator session possible
A WordPress site is affected if the wp-database-backup plugin is installed and active with a version lower than 4.3.1, allowing CSRF attacks against authenticated administrators.
Generated from the published advisory. Verify against your own configuration.
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 data4.3.1
Update the wp-database-backup plugin to version 4.3.1 or later, which should include proper anti-CSRF token validation for state-changing operations.
Fix this in Wp Database Backup
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10876 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-10876 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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