Wp Database BackupWordPress extension · Wpseeds
CVE-2016-10873
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.3 for WordPress has XSS.
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 · moderate confidenceCross-site scripting (XSS) vulnerability in the wp-database-backup plugin for WordPress versions prior to 4.3.3, allowing attackers to inject malicious scripts through unspecified input fields.
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.3CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Identify the installed plugin versionIn the WordPress admin dashboard, go to Plugins > Installed Plugins. Locate the 'wp-database-backup' or 'Wpseeds Wp Database Backup' plugin and note the version number displayed.Affected if The displayed version number is lower than 4.3.3
-
Confirm the plugin is activeIn the WordPress admin under Plugins > Installed Plugins, verify whether wp-database-backup shows as 'Active' rather than 'Inactive' or 'Plugin file not found'.Affected if The plugin is active and the version is below 4.3.3
-
Check for unknown administrator accountsIn the WordPress admin, go to Users > All Users and review the list for any unfamiliar administrator accounts that were not created by known site administrators.Affected if Unexpected admin accounts exist, suggesting possible XSS exploitation leading to account creation
-
Review plugin for unauthorized file modificationsAccess the wp-content/plugins/wp-database-backup directory via file manager or FTP. Compare file hashes or timestamps against a known clean version, or inspect PHP files for suspicious encoded code or eval() calls.Affected if Files have been modified or contain unexpected code, indicating potential compromise through the XSS vulnerability
You are affected if the wp-database-backup plugin is active and its installed version is below 4.3.3, or if post-compromise indicators like unknown admin accounts or modified plugin files are found.
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.3
Update the wp-database-backup plugin to version 4.3.3 or later to patch the XSS vulnerability, and review admin/user sessions for compromise.
Fix this in Wp Database Backup
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10873 — 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-10873 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