Security readout for executives and security teams
Plain-English summary
This CVE affects the WordPress user-domain-whitelist plugin before version 1.5. The reported issue is cross-site request forgery, meaning a logged-in administrator could potentially be tricked into making an unwanted change. The public bundle provides no CVSS score, impact detail, or evidence of active exploitation.
Executive priority
Do not treat this as an internet-wide emergency based on the provided evidence. Prioritize inventory first, then remediate any confirmed pre-1.5 installations as part of WordPress plugin risk reduction.
Technical view
CVE-2014-10381 is a CSRF flaw in user-domain-whitelist for WordPress before 1.5. The available sources do not describe the vulnerable request, affected action, privilege requirements beyond the CSRF model, or confirmed fixed code. Treat version comparison and vendor changelog review as the primary validation path.
Likely exposure
Exposure is limited to WordPress sites that installed the user-domain-whitelist plugin and are running a version before 1.5. The bundle does not identify affected CPEs or broader product families.
Exploitation context
The source bundle does not show KEV listing or cited evidence of exploitation in the wild. CSRF generally depends on a legitimate logged-in user being induced to trigger an unintended action, but this CVE’s exact impact is not described.
Researcher notes
Public detail is sparse: no CVSS, CWE, affected CPE, vulnerable endpoint, or exploit narrative is included. Analysis should stay constrained to plugin presence, version state, changelog confirmation, and local configuration impact.
Mitigation direction
- Inventory WordPress sites for the user-domain-whitelist plugin.
- Upgrade installations below version 1.5 where an update is available.
- Remove the plugin if it is unused or cannot be updated.
- Check vendor plugin guidance before relying on compensating controls.
Validation and detection
- Confirm whether the plugin is installed on each WordPress site.
- Record the installed plugin version and compare it against 1.5.
- Review the plugin developer changelog for the CSRF fix reference.
- Check admin activity logs for unexpected whitelist configuration changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2014-10381 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wordpress.org/plugins/user-domain-whitelist/#developersCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.