CVE-2026-109513 wpdevteam CVE debrief

Who should care

Defenders responsible for WordPress installations with the NotificationX plugin should assess exposure and prioritize verification of plugin versions and access controls. They should also review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance, and plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Why it matters

CVE-2026-109513 allows unauthenticated Stored Cross-Site Scripting in the NotificationX WordPress plugin. Defenders should verify plugin versions, restrict access to Reviews campaign configuration, and monitor public pages for suspicious activity.

• Unauthenticated attackers can inject web scripts in public pages
• Requires administrator action to enable Reviews campaign and place dynamic block
• Injected scripts execute when users access affected pages

Technical summary

The NotificationX plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'name' parameter in all versions up to, and including, 3.3.3. This is due to insufficient input sanitization and output escaping. An attacker can inject arbitrary web scripts in pages that will execute when a user accesses an injected page, but only if an administrator has previously enabled a WordPress.org Reviews campaign and placed the notificationx-pro/notificationx dynamic block on a public page.

Defensive priority

Defenders should prioritize verifying plugin versions and restricting access to the WordPress.org Reviews campaign configuration.

Recommended defensive actions

• Verify plugin version and update to a fixed version if available
• Restrict access to the WordPress.org Reviews campaign configuration
• Monitor for suspicious activity on public pages with the dynamic block
• 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 vulnerability exists in the NotificationX plugin, specifically in the handling of the 'name' parameter. This requires an administrator to have enabled a WordPress.org Reviews campaign and placed a dynamic block on a public page.

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.