Security readout for executives and security teams
Plain-English summary
CVE-2015-9416 is a cross-site scripting issue in older WPML WordPress plugin versions. Affected sites could expose users or administrators to malicious browser-side content if the vulnerable Accept-Language header handling is reached. The provided sources do not give a CVSS score, patch version, or confirmed exploitation.
Executive priority
Prioritize inventory first. Business urgency depends on whether affected WPML versions still exist on public WordPress sites, because the provided sources do not establish severity, exploitation, or a named fix.
Technical view
The issue affects sitepress-multilingual-cms, also known as WPML, versions 2.9.3 through 3.2.6. The reported vector is XSS via the HTTP Accept-Language header. No CWE, CVSS vector, proof details, or remediation version is included in the provided source bundle.
Likely exposure
Exposure is limited to WordPress sites using WPML/sitepress-multilingual-cms versions 2.9.3 through 3.2.6. Organizations not running WPML, or running versions outside that range, are not shown as affected by the provided sources.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. Treat this as a known historical WordPress plugin XSS until asset inventory confirms whether affected versions remain deployed.
Researcher notes
The record is sparse: affected version range and header-based XSS vector are stated, but severity, CWE, exploitability conditions, authentication requirements, and fixed version are not provided. Avoid assuming active exploitation or a specific patch level without vendor confirmation.
Mitigation direction
- Inventory WordPress sites for WPML/sitepress-multilingual-cms installations.
- Identify any WPML versions from 2.9.3 through 3.2.6.
- Consult WPML or WordPress plugin guidance for supported non-affected versions.
- Remove the plugin where it is unused or no longer business-critical.
- Review WAF and logging coverage for suspicious header-based XSS attempts.
Validation and detection
- Check WordPress admin or plugin manifests for installed WPML versions.
- Confirm whether any internet-facing sites run affected versions.
- Review access logs for unusual Accept-Language header patterns.
- Verify remediation by confirming affected versions are no longer deployed.
- Document any exceptions with compensating controls and owner approval.
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-9416 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/8173CVE reference · x_refsource_MISC
- https://wordpress.org/plugins/sitepress-multilingual-cms/#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.