WP Bannerize Pro <= 1.9.0 - Authenticated (Editor+) Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 1.9.1
- Affected Plugin
- WP Bannerize Pro
- Affected Version
<= 1.9.0- CVSS
- 4.0Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2024-7388
At a glance
CVE-2024-7388 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP Bannerize Pro WordPress plugin, affecting versions <= 1.9.0. It carries a CVSS score of 4.0 (reachable over the network). Exploitation requires an authenticated account at Editor level or above. The issue is fixed in version 1.9.1; sites on affected versions should update now. Disclosed August 2024, reported by Nguyễn Trung Kiên.
Vulnerability Overview
The WP Bannerize Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via banner alt data in all versions up to, and including, 1.9.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with editor-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
Technical Analysis
The vector marks this flaw as remotely reachable over the network.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in WP Bannerize Pro <= 1.9.0 takes an account at Editor level or above. 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 WP Bannerize Pro the fix is 1.9.1: builds <= 1.9.0 are affected, anything from 1.9.1 onward is not.
Remediation
Update to version 1.9.1, or a newer patched version
How does WordSec protect against this?
An attacker needs Editor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Bannerize Pro 1.9.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C