CVE-2026-110721 json
NotificationX <= 3.3.3 - Missing Authorization to Unauthenticated Arbitrary Content Injection via 'nx_id' Parameter on /popup-submit REST Route
published 24d ago modified 24d ago also EUVD-2026-102642
- cvss
- 5.3
- 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 plugin for WordPress is vulnerable to Missing Authorization leading to arbitrary content injection in versions up to, and including, 3.3.3 The /notificationx/v1/popup-submit REST route is registered with permission_callback => '__return_true', and the handler at PopupNotification::handle_popup_submission() accepts an attacker-controlled nx_id, loads whichever NotificationX campaign that id points to, and copies that campaign's own source into the new entry without verifying that the campaign is a Popup Notification or Exit Intent Popup (the two sources this form is intended to serve). This makes it possible for unauthenticated attackers to inject forged social-proof entries (name, title, message, email, theme) into any enabled non-popup NotificationX campaign — WP Comments, WooCommerce/EDD/Give sales, reviews, etc.
Is CVE-2026-110721 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
- yes
- Technical impact
- partial
- Assessed
- 24d ago
Exploit prediction
0.25% 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 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/84b5e044-4522-480a-ad14-8886ed691a86?source=cve
- plugins.trac.wordpress.org /browser/notificationx/tags/3.3.3/includes/Extensions/PopupNotification/PopupNotification.php#L1161
- plugins.trac.wordpress.org /browser/notificationx/tags/3.3.3/includes/Extensions/Extension.php#L668
- plugins.trac.wordpress.org /browser/notificationx/tags/3.3.3/includes/Core/Rest/Popup.php#L58
- plugins.trac.wordpress.org /browser/notificationx/tags/3.3.3/includes/Core/Rest/Popup.php#L186
- plugins.trac.wordpress.org /browser/notificationx/tags/3.3.3/includes/Admin/Entries.php#L93
- plugins.trac.wordpress.org /changeset/3746251/notificationx/trunk/includes/Extensions/PopupNotification/PopupNotification.php
Sources
- CVE List CVE-2026-110721
- NVD CVE-2026-110721
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.