Security readout for executives and security teams
Plain-English summary
CVE-2014-10395 is a cross-site scripting issue in the WordPress cp-polls plugin before version 1.0.1. The limited public record says the flaw is in the votes list, but does not provide CVSS, attacker requirements, or confirmed impact. Organizations should treat exposure as plugin-specific and verify whether the plugin is installed.
Executive priority
Prioritize this as a targeted WordPress plugin exposure check, not a broad enterprise emergency. If cp-polls is absent, no action is needed. If present below 1.0.1, remediate promptly because XSS can affect user trust and administrator sessions.
Technical view
The source bundle describes XSS in the cp-polls WordPress plugin votes list for versions before 1.0.1. No CWE, CVSS vector, affected CPE, exploit details, or vendor advisory text is included. The version boundary suggests pre-1.0.1 installations are the relevant exposure scope, pending confirmation from WordPress plugin metadata.
Likely exposure
Exposure is likely limited to WordPress sites that installed cp-polls before version 1.0.1 and still have it active or reachable. The public record does not identify affected configurations beyond the plugin and version boundary.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation. XSS in a votes list may require access to the plugin’s polling or administrative workflow, but the source bundle does not prove prerequisites.
Researcher notes
Evidence is sparse: the bundle provides the CVE description, WordPress plugin reference, and version boundary only. Do not assume unauthenticated exploitation, stored versus reflected behavior, or exploit availability without additional primary-source confirmation.
Mitigation direction
- Inventory WordPress sites for the cp-polls plugin and installed version.
- Update cp-polls to 1.0.1 or later if vendor guidance confirms availability.
- Disable or remove cp-polls where it is unused or cannot be updated.
- Review WordPress plugin changelog or vendor guidance before production remediation.
Validation and detection
- Check WordPress plugin inventory for cp-polls installations below version 1.0.1.
- Confirm whether cp-polls is active on public or internal WordPress sites.
- Review administrative votes-list access controls and relevant user roles.
- Look for unexpected script content in poll vote records or plugin data.
- Document findings because the public CVE record lacks CVSS and detailed scope.
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-10395 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/cp-polls/#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.