Authorize.net Add-on for iThemes Exchange < 1.1.0 - Reflected Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.1.0
- Affected Plugin
- Authorize.net Add-on for iThemes Exchange
- Affected Version
< 1.1.0- CVSS
- 6.1Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2015-9365
At a glance
CVE-2015-9365 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Authorize.net Add-on for iThemes Exchange WordPress plugin, affecting versions < 1.1.0. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.0; sites on affected versions should update now. Disclosed April 2015, reported by Sucuri Research Team.
Vulnerability Overview
Authorize.net Add-on for iThemes Exchange before 1.1.0 for WordPress has XSS via add_query_arg() and remove_query_arg().
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Authorize.net Add-on for iThemes Exchange < 1.1.0 carries this weakness at add_query_arg(), and reaching it takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Authorize.net Add-on for iThemes Exchange the fix is 1.1.0: builds < 1.1.0 are affected, anything from 1.1.0 onward is not.
Remediation
Update to version 1.1.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Authorize.net Add-on for iThemes Exchange: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Authorize.net Add-on for iThemes Exchange 1.1.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C