Security readout for executives and security teams
Plain-English summary
This CVE reports cross-site scripting in the WordPress Relevant plugin before 1.0.8. XSS can let attacker-controlled content run in a visitor's browser, but the provided sources do not describe the vulnerable page, required privileges, or impact details.
Executive priority
Handle as a targeted WordPress hygiene issue. Prioritize internet-facing or business-critical sites where the plugin is installed, but avoid escalating to emergency response without more evidence of exploitation or severe impact.
Technical view
The public record only states XSS in the Relevant WordPress plugin versions before 1.0.8. No CVSS score, CWE, vulnerable parameter, authentication requirement, or proof-of-concept detail is provided in the source bundle.
Likely exposure
Exposure is likely limited to WordPress sites with the Relevant plugin installed below version 1.0.8. The sources do not identify affected configurations beyond that version boundary.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. Exploitability cannot be assessed from the available record.
Researcher notes
The record is sparse. Useful missing details include sink/source, affected endpoint, privilege requirement, stored versus reflected XSS, and fix commit. Do not assume broader WordPress impact beyond the named plugin and version range.
Mitigation direction
- Inventory WordPress sites for the Relevant plugin and record installed versions.
- Update the plugin to 1.0.8 or later where it is installed.
- If updates are unavailable, consult the WordPress plugin page or vendor guidance.
- Restrict plugin administration to trusted users until remediation is confirmed.
Validation and detection
- Confirm whether the Relevant plugin is present on each WordPress site.
- Check whether any installed version is earlier than 1.0.8.
- Verify the plugin update completed successfully and remains enabled only if needed.
- Review web logs and WordPress audit trails for suspicious script-injection activity.
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-9384 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://wpvulndb.com/vulnerabilities/8361CVE reference · x_refsource_MISC
- https://wordpress.org/plugins/relevant/#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.