Wp Database BackupWordPress extension · Wpseeds
CVE-2019-14949
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 5.1.2 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 · high confidenceThe wp-database-backup WordPress plugin before version 5.1.2 contains a Cross-Site Scripting (XSS) vulnerability that allows attackers to inject malicious scripts through the plugin interface.
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
< 5.1.2CVSS 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.
-
Locate the wp-database-backup plugin installationCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'wp-database-backup' or similar variant. Alternatively, log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to list all plugins.Affected if The plugin folder exists in wp-content/plugins/ or the plugin appears in the WordPress admin plugins list.
-
Identify the installed plugin versionIn the WordPress admin, find the wp-database-backup plugin in the Installed Plugins list and read the version number displayed beneath the plugin name. Alternatively, inspect the main plugin PHP file (often wp-database-backup.php) or readme.txt file within the plugin folder for a 'Version:' header.Affected if The displayed version number is lower than 5.1.2 (for example, 5.1.1, 5.0, or any version before 5.1.2).
-
Verify the plugin is activeIn WordPress admin > Plugins > Installed Plugins, confirm whether wp-database-backup shows as 'Active' (not 'Inactive' or 'Must Use'). Alternatively, query the WordPress options table in the database for the option_name 'active_plugins'.Affected if The plugin status shows as 'Active' and is included in the active_plugins array in the database.
-
Confirm the plugin author is WpseedsIn the plugin list within WordPress admin, note the 'By' author line next to wp-database-backup. Alternatively, inspect the plugin header in the main PHP file for 'Author: Wpseeds' or check the plugin's readme.txt for author details.Affected if The author is listed as Wpseeds and the version is below 5.1.2, indicating this specific vulnerable plugin rather than a similarly-named alternative.
The environment is affected if the wp-database-backup plugin by Wpseeds is installed, active, and its version is lower than 5.1.2, as only this combination enables the XSS attack vector through the plugin interface.
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 data5.1.2
Update the wp-database-backup plugin to version 5.1.2 or later to patch the XSS 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
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-2019-14949 — 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-2019-14949 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