Live › vulnerability › CVE-2026-109513
Go to dashboardThe NotificationX WordPress plugin up to and including 3.3.3 does not sanitize the 'name' parameter, so unauthenticated attackers can store script that runs in visitors' browsers on pages showing the notification block. The injected script runs whenever a user loads an affected public page.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Sites running NotificationX 3.3.3 or earlier where an administrator has enabled a WordPress.org Reviews campaign and placed the notificationx dynamic block on a public page. Sites without that campaign or block on public pages are not exposed through this path.
No product ranges from the sources yet.
wp plugin get notificationx --field=version3.3.3 (the first fixed version is unknown from the sources)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The NotificationX – FOMO, Live Sales Notification, WooCommerce Sales Popup, GDPR, Social Proof, Announcement Banner & Floating Notification Bar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'name' parameter in all versions up to, and including, 3.3.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires that an administrator has previously enabled a WordPress.org Reviews campaign and placed the notificationx-pro/notificationx dynamic block on a public page, both of which are documented, supported plugin workflows.
This page as .md · .json · in your agent: get_signal("CVE-2026-109513")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.