# CVE-2026-110721: NotificationX plugin for WordPress missing authorization in REST API

Source: https://junglewise.ai/threats/cve-2026-110721-the-notificationx-plugin-for-wordpress-is-vulnerable-to-missing  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-16. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-110721 · Severity: medium · CVSS 5.3 · Published 2026-10-16

The NotificationX plugin for WordPress, used to display notifications and social proof on websites, has a security flaw in its REST API that allows unauthenticated attackers to inject fake testimonials, reviews, or sales notifications into any campaign. This can damage site credibility, mislead visitors, and potentially spread malicious content without administrator approval.

Technologies: [NotificationX](https://junglewise.ai/threats/technologies/notificationx). Vendors: [NotificationX](https://junglewise.ai/threats/vendors/notificationx).

## Quick answers

**Is CVE-2026-110721 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-110721 being exploited in the wild.

**How severe is CVE-2026-110721?** Medium severity, with a CVSS score of 5.3, published 16 October 2026.

**Which products and versions are affected?** NotificationX up to and including 3.3.3.

**Is there a fix for CVE-2026-110721?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-110721 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-110721?** Check whether you run NotificationX at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The /notificationx/v1/popup-submit REST endpoint lacks proper authorization checks (uses permission_callback => '__return_true') and does not validate that attacker-supplied campaign IDs correspond to legitimate popup sources before injecting user-controlled content into them. An unauthenticated attacker can bypass these controls to inject forged entries (name, title, message, email, theme) into any enabled non-popup campaign type (WP Comments, WooCommerce sales, reviews, etc.).

## Affected products

- NotificationX NotificationX up to and including 3.3.3

## Timeline

- 2026-10-16: disclosed

## References

- [https://plugins.trac.wordpress.org/browser/notificationx/tags/3.3.3/includes/Admin/Entries.php](https://plugins.trac.wordpress.org/browser/notificationx/tags/3.3.3/includes/Admin/Entries.php)
- [https://plugins.trac.wordpress.org/browser/notificationx/tags/3.3.3/includes/Core/Rest/Popup.php](https://plugins.trac.wordpress.org/browser/notificationx/tags/3.3.3/includes/Core/Rest/Popup.php)

## Related threats

- [NotificationX WordPress plugin unauthenticated content disclosure and shortcode execution](https://junglewise.ai/threats/cve-2026-119302-the-notificationx-wordpress-plugin-before-3-3-7-does-not-perform)
- [NotificationX WordPress plugin unauthenticated settings update and email sending](https://junglewise.ai/threats/cve-2026-119303-the-notificationx-wordpress-plugin-before-3-3-7-does-not-perform)
- [NotificationX stored cross-site scripting in name parameter](https://junglewise.ai/threats/cve-2026-109513-the-notificationx-fomo-live-sales-notification-woocommerce-sales)