WPFront Notification Bar <= 3.5.1 - Reflected Cross-Site Scripting via REQUEST_URI
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The WPFront Notification Bar plugin for WordPress is vulnerable to Reflected Cross-Site Scripting in versions up to, and including, 3.5.1. This is due to the debug-log output path (write_debug_logs) reflecting the raw value of $_SERVER['REQUEST_URI'] through vprintf() directly inside a <script> block emitted on wp_footer, without any sanitization or escaping (see the 'Current URL is "%s"' log entry produced by the URL-text display filter in the filter() method). This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a specially crafted link.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- syammohanm WPFront Notification Bar
through 3.5.1
References 5
plugins.trac.wordpress.org
- browser/wpfront-notification-bar/tags/3.5.1/classes/class-wpfront-notification-bar-controller.php#L327
- browser/wpfront-notification-bar/tags/3.5.1/classes/class-wpfront-notification-bar-controller.php#L491
- browser/wpfront-notification-bar/tags/3.5.1/classes/class-wpfront-notification-bar-controller.php#L843
- changeset?reponame=&old=3722432%40wpfront-notification-bar&new=3722432%40wpfront-notification-bar