Security readout for executives and security teams
Plain-English summary
This CVE describes a cross-site scripting flaw in the Authorize.net Add-on for iThemes Exchange for WordPress before version 1.1.0. Affected sites could expose users or administrators to script execution in the browser. The source bundle does not provide CVSS, exploit details, or confirmed active exploitation.
Executive priority
Treat this as a targeted WordPress plugin hygiene issue, not a confirmed emergency. Prioritize internet-facing commerce sites and administrator-used WordPress environments because XSS can support account compromise or session abuse.
Technical view
The issue is reported as XSS caused by unsafe use of WordPress add_query_arg() and remove_query_arg() handling in plugin versions before 1.1.0. The available sources do not specify the vulnerable endpoint, authentication requirements, XSS type, or exact patch diff.
Likely exposure
Exposure is likely limited to WordPress sites that installed the Authorize.net Add-on for iThemes Exchange and have not updated past 1.1.0. Sites without that add-on are not indicated as affected by the provided sources.
Exploitation context
The CVE is not listed as CISA KEV in the source bundle, and no cited source confirms active exploitation. Public references describe a coordinated WordPress plugin XSS update, but the bundle lacks exploit maturity details.
Researcher notes
The source bundle is sparse. It names the vulnerable plugin and version boundary but omits CVSS, CWE, endpoint, prerequisites, and exploit status. Avoid assuming broader iThemes Exchange impact without separate source evidence.
Mitigation direction
- Update the add-on to version 1.1.0 or later if installed.
- Remove the add-on if it is unused or no longer maintained.
- Check iThemes vendor guidance for any additional remediation notes.
- Review WordPress plugin inventory for stale payment-related extensions.
Validation and detection
- Confirm whether the affected add-on is installed on each WordPress site.
- Record the installed plugin version and compare it with 1.1.0.
- Review vendor advisory history for the specific deployed package.
- Check web and admin logs for unusual requests to plugin-related pages.
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-9365 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.