Security readout for executives and security teams
Plain-English summary
This CVE concerns a cross-site scripting issue in the iThemes Builder Style Manager WordPress plugin before version 0.7.7. A vulnerable site could expose users or administrators to unwanted script execution in the browser. The bundle does not provide CVSS, confirmed exploitation, or detailed impact evidence.
Executive priority
Treat this as a targeted WordPress hygiene item, not an enterprise-wide emergency from the supplied evidence. Prioritize remediation where the plugin exists on public or administrator-used sites, especially if WordPress administration is exposed to untrusted users.
Technical view
The issue is described as XSS related to WordPress add_query_arg() and remove_query_arg() usage in iThemes Builder Style Manager before 0.7.7. The supplied data does not include request vectors, authentication requirements, affected CPEs, or CVSS scoring, so validation should focus on installed plugin version and vendor advisory alignment.
Likely exposure
Exposure is likely limited to WordPress sites that installed iThemes Builder Style Manager before 0.7.7. The source bundle lists affected vendor/product metadata as n/a and provides no CPEs, so asset discovery must rely on WordPress plugin inventories rather than standardized platform matching.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. Public references describe a coordinated WordPress plugin security update and a Sucuri advisory, but the provided data does not establish exploitation in the wild or provide exploit maturity.
Researcher notes
The record lacks CVSS, CWE, CPE, detailed sink/source analysis, and exploitability conditions. Do not assume all iThemes products are affected. Scope specifically to Builder Style Manager before 0.7.7 and document any local findings separately from the CVE data.
Mitigation direction
- Inventory WordPress sites for iThemes Builder Style Manager installations.
- Upgrade vulnerable installations to version 0.7.7 or later where available.
- If updates are unavailable, disable or remove the plugin pending vendor guidance.
- Prioritize administrator-facing WordPress sites because XSS can target privileged sessions.
Validation and detection
- Confirm the installed plugin version on every WordPress instance.
- Check whether any installation is earlier than 0.7.7.
- Review vendor and Sucuri advisories for current remediation guidance.
- Look for unexpected script content or suspicious admin-session activity around affected sites.
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-9379 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://blog.sucuri.net/2015/04/security-advisory-xss-vulnerability-affecting-multiple-wordpress-plugins.htmlCVE reference · x_refsource_MISC
- https://ithemes.com/coordinated-wordpress-plugin-security-update/CVE 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.
