Security readout for executives and security teams
Plain-English summary
CVE-2015-9347 is a cross-site scripting issue in the WordPress wp-plotly plugin before version 1.0.3. The available description says authors can trigger it, so the main concern is sites where untrusted or semi-trusted users can publish or edit content.
Executive priority
Treat this as a targeted hygiene issue, not an emergency based on current evidence. Prioritize multi-author WordPress sites because the reported trigger requires author privileges and could affect visitor or admin trust in site content.
Technical view
The source bundle identifies an XSS vulnerability in wp-plotly before 1.0.3 for WordPress, described as exploitable by authors. No CVSS score, CWE, exploit details, or detailed affected version matrix is provided beyond the version boundary.
Likely exposure
Exposure appears limited to WordPress sites using wp-plotly versions earlier than 1.0.3, especially multi-author environments. The bundle does not identify affected CPEs, hosting patterns, or whether the plugin remains deployed in current environments.
Exploitation context
The bundle does not show active exploitation, and KEV status is false. Evidence only supports an authenticated author-level XSS scenario, without public exploit status, attack complexity, or impact details.
Researcher notes
Evidence is sparse. The only vulnerability detail is XSS in wp-plotly before 1.0.3 by authors. Avoid assuming unauthenticated exploitation, broader WordPress impact, or a specific sanitization flaw without reviewing the plugin changelog or source diff.
Mitigation direction
- Inventory WordPress sites for the wp-plotly plugin.
- Upgrade wp-plotly from versions before 1.0.3 where available.
- If upgrade is unavailable, review vendor plugin guidance.
- Disable or remove unused wp-plotly installations.
- Restrict author access to trusted users only.
Validation and detection
- Check WordPress plugin inventory for wp-plotly.
- Confirm installed wp-plotly version is 1.0.3 or later.
- Review sites with untrusted author accounts first.
- Check whether vulnerable sites allow author-generated Plotly content.
- Document any instances that cannot be upgraded.
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-2015-9347 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/wp-plotly/#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.