Custom Banners < 2.1 - Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.1
- Affected Plugin
- Custom Banners
- Affected Version
< 2.1- CVSS
- 7.1High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2014-4724
At a glance
CVE-2014-4724 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Custom Banners 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 June 2014, reported by Ashiyane Digital Security Team.
Vulnerability Overview
Cross-site scripting (XSS) vulnerability in the Custom Banners plugin before 2.1 for WordPress allows remote attackers to inject arbitrary web script or HTML via the custom_banners_registered_name parameter to wp-admin/options.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 Custom Banners < 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 Custom Banners 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 Custom Banners: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Custom Banners 2.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Custom Banners
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C