Security readout for executives and security teams
Plain-English summary
This is an old cross-site scripting issue in Web Dorado Spider Video Player, also called WordPress Video Player. Sites running plugin versions before 1.5.2 could allow a remote attacker to inject script or HTML. The source record does not name active exploitation or provide a CVSS score.
Executive priority
Treat as a targeted hygiene issue for legacy WordPress estates. Prioritize any public site still using the plugin, especially where administrators access the same site while logged in.
Technical view
CVE-2014-8584 describes XSS in the WordPress plugin before version 1.5.2. The CVE says remote attackers can inject arbitrary web script or HTML through unspecified vectors. The affected configuration and exact entry point are not detailed in the provided sources.
Likely exposure
Exposure is likely limited to WordPress sites that installed Web Dorado Spider Video Player and remain below version 1.5.2. Sites without this plugin are not indicated as affected by the sources.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not cite active exploitation. Risk depends on whether vulnerable plugin output is reachable and whether injected content can execute for privileged users or visitors.
Researcher notes
The public record lacks CVSS, CWE, affected CPEs, and vector detail. Analysis should remain conservative: confirm plugin presence and version first, then use vendor changelog information for remediation decisions.
Mitigation direction
- Inventory WordPress sites for the Spider Video Player plugin.
- Upgrade affected installations to version 1.5.2 or later.
- If upgrade is not possible, remove or disable the plugin.
- Check the vendor changelog and current plugin guidance.
Validation and detection
- Confirm whether the plugin is installed on each WordPress site.
- Record the installed plugin version and compare it with 1.5.2.
- Review web logs for suspicious requests to plugin-related pages.
- Verify remediation by confirming the plugin is absent or at least 1.5.2.
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-8584 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/player/changelogCVE reference · x_refsource_CONFIRM
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.