CVE-2026-109513 json
NotificationX <= 3.3.3 - Unauthenticated Stored Cross-Site Scripting via 'name' Parameter via popup-submit REST Route
published 24d ago modified 24d ago also EUVD-2026-102678
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-109513 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 24d ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- wpdevteam NotificationX – FOMO, Live Sales Notification, WooCommerce Sales Popup, GDPR, Social Proof, Announcement Banner & Floating Notification Bar
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/cac6c4f3-ac60-45d6-a5ba-6708fc1491a4?source=cve
- plugins.trac.wordpress.org /browser/notificationx/tags/3.3.3/blocks/Blocks.php#L218
- plugins.trac.wordpress.org /browser/notificationx/tags/3.3.3/includes/Features/ShortcodeInline.php#L148
- plugins.trac.wordpress.org /browser/notificationx/tags/3.3.3/includes/Extensions/WordPress/WPOrgReview.php#L295
- plugins.trac.wordpress.org /browser/notificationx/tags/3.3.3/includes/Core/Rest/Popup.php#L55
- plugins.trac.wordpress.org /browser/notificationx/tags/3.3.3/includes/Extensions/PopupNotification/PopupNotification.php#L1119
- plugins.trac.wordpress.org /changeset?reponame=&new=3746251%40notificationx%2Ftags%2F3.3.4&old=3720837%40notificationx%2Ftags%2F3.3.3
Sources
- CVE List CVE-2026-109513
- NVD CVE-2026-109513
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.