WonderPlugin Audio Player < 2.1 - Multiple Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.1
- Affected Plugin
- WonderPlugin Audio Player
- Affected Version
< 2.1- CVSS
- 7.1High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2015-2218
At a glance
CVE-2015-2218 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WonderPlugin Audio Player WordPress plugin, affecting versions < 2.1. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.1; sites on affected versions should update now. Disclosed February 2015, reported by Kacper Szurek.
Vulnerability Overview
Multiple cross-site scripting (XSS) vulnerabilities in the wp_ajax_save_item function in wonderpluginaudio.php in the WonderPlugin Audio Player plugin before 2.1 for WordPress allow remote attackers to inject arbitrary web script or HTML via the (1) item[name] or (2) item[customcss] parameter in a wonderplugin_audio_save_item action to wp-admin/admin-ajax.php or the itemid parameter in the (3) wonderplugin_audio_show_item or (4) wonderplugin_audio_edit_item page to wp-admin/admin.php.
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')
Reaching this weakness in WonderPlugin Audio Player < 2.1 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 WonderPlugin Audio Player the fix is 2.1: builds < 2.1 are affected, anything from 2.1 onward is not.
Remediation
Update to version 2.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WonderPlugin Audio Player: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WonderPlugin Audio Player 2.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WonderPlugin Audio Player
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C