Security readout for executives and security teams
Plain-English summary
A WordPress add-on used with iThemes Exchange could allow attacker-controlled script to run in a user's browser. The source bundle provides no CVSS, no KEV listing, and no active exploitation evidence. Treat this as legacy WordPress plugin risk requiring inventory, update, or removal.
Executive priority
Prioritize as a moderate cleanup item for WordPress assets, especially ecommerce or administrator-facing sites. Lack of active exploitation evidence reduces urgency, but XSS in legacy plugins can still create account and content integrity risk.
Technical view
CVE-2015-9369 describes XSS in Easy US Sales Taxes Add-on for iThemes Exchange before 1.1.0 involving add_query_arg() and remove_query_arg(). The provided sources do not specify the XSS context, affected endpoint, privileges required, or complete exploit conditions.
Likely exposure
Exposure is likely limited to WordPress sites that installed Easy US Sales Taxes Add-on for iThemes Exchange before version 1.1.0. Sites without that add-on are not indicated as affected by the provided sources.
Exploitation context
The bundle does not show CISA KEV inclusion or cited active exploitation. Public references describe a coordinated WordPress plugin XSS update, but do not provide evidence here of exploitation in the wild.
Researcher notes
The evidence is thin: no CVSS, CWE, endpoint, privilege requirement, or exploitability detail is included. Base validation on plugin presence and version, not offensive reproduction. Use vendor and Sucuri references for historical context.
Mitigation direction
- Inventory WordPress sites for the affected iThemes Exchange tax add-on.
- Update the add-on to version 1.1.0 or later where available.
- Remove or disable the add-on if it is unused or unsupported.
- Check vendor guidance for any additional hardening or replacement advice.
Validation and detection
- Confirm installed plugin name and version from WordPress administration or asset records.
- Verify whether any site runs a version earlier than 1.1.0.
- Review web application logs for unusual plugin-related requests around administrative sessions.
- Document findings even when the plugin is absent to close exposure tracking.
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-9369 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.