CVE-2026-110721 wpdevteam CVE debrief

Who should care

Defenders responsible for WordPress deployments using the NotificationX plugin should assess exposure and prioritize verification of the plugin version and restriction of access to the vulnerable REST route.

Why it matters

The NotificationX plugin vulnerability allows unauthenticated attackers to inject forged social-proof entries, requiring defenders to verify plugin versions and restrict access to the vulnerable REST route.

• Defenders must verify the version of the NotificationX plugin to determine exposure
• Unauthenticated attackers can inject forged social-proof entries into NotificationX campaigns
• Defenders should restrict access to the /notificationx/v1/popup-submit REST route to prevent exploitation
• The scope of affected versions and deployments requires further verification

Technical summary

The NotificationX plugin for WordPress registers the /notificationx/v1/popup-submit REST route with permission_callback => '__return_true', allowing unauthenticated attackers to inject forged social-proof entries into any enabled non-popup NotificationX campaign. The plugin 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. This makes it possible for unauthenticated attackers to inject forged social-proof entries into any enabled non-popup NotificationX campaign — WP Comments, WooCommerce/EDD/Give sales, reviews, etc.

Defensive priority

Defenders should prioritize verifying the version of the NotificationX plugin and restricting access to the /notificationx/v1/popup-submit REST route.

Recommended defensive actions

• Verify the version of the NotificationX plugin and update to a patched version if necessary
• Restrict access to the /notificationx/v1/popup-submit REST route
• Monitor for suspicious activity on the NotificationX plugin
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source references indicate that the NotificationX plugin is vulnerable to missing authorization, allowing unauthenticated attackers to inject forged social-proof entries. However, the exact scope of affected versions and deployments requires further verification.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.