dbcve.org
User Domain WhitelistWordPress extension · User Domain Whitelist Project

CVE-2014-10381

HIGH · 8.8 CVSS v3.0 Published 2019-08-20
Fix available
A fix is available. Upgrade to 1.5 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 user-domain-whitelist plugin before 1.5 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 · moderate confidence

The user-domain-whitelist WordPress plugin before version 1.5 contains a Cross-Site Request Forgery (CSRF) vulnerability. This allows attackers to trick authenticated administrators into performing unintended configuration changes to the plugin's domain whitelist settings by crafting malicious requests.

MitigationUpdate the user-domain-whitelist plugin to version 1.5 or later. If immediate update is not possible, consider deactivating the plugin until the patch can be applied.

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
User Domain WhitelistWordPress extension
Affected:< 1.5

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.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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'user-domain-whitelist' or look for the plugin in the WordPress admin under Plugins > Installed Plugins.
    Affected if The plugin folder exists or the plugin is listed in the WordPress admin.
  2. Determine installed version
    Access the plugin's main PHP file (usually user-domain-whitelist.php) and look for the 'Version' field in the plugin header, or view the plugin details in the WordPress admin.
    Affected if The version number is less than 1.5.
  3. Confirm plugin activation
    In the WordPress admin, go to Plugins > Installed Plugins and check if User Domain Whitelist is activated.
    Affected if The plugin is activated.
  4. Inspect domain whitelist settings
    Navigate to the plugin's settings page (usually under Settings > User Domain Whitelist) and check if the settings are accessible.
    Affected if The plugin is active and the settings page is accessible, making the CSRF vulnerability exploitable.

The environment is affected if the User Domain Whitelist plugin is installed with a version less than 1.5 and is active, allowing authenticated administrators to be targeted by CSRF attacks.

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 1.5 or later
Fixed in 1.5
Interim mitigation

Update the user-domain-whitelist plugin to version 1.5 or later. If immediate update is not possible, consider deactivating the plugin until the patch can be applied.

Fix this in User Domain Whitelist Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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