Is CVE-2026-109513 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-109513 being exploited in the wild.

How severe is CVE-2026-109513?

High severity, with a CVSS score of 7.2, 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-109513?

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-109513 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-109513?

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.

CVE-2026-109513: NotificationX stored cross-site scripting in name parameter

CVE-2026-109513 · Severity: high · CVSS 7.2 · Published 2026-10-16

NotificationX is a WordPress plugin that adds notification banners and sales popups to e-commerce and content sites. The plugin fails to sanitize user input in the name parameter, allowing attackers to inject malicious scripts that execute when site visitors view affected pages. Exploitation requires that an administrator has already enabled a WordPress.org Reviews campaign and placed the notificationx dynamic block on a public page.

Technologies: NotificationX. Vendors: NotificationX.

Quick answers

Is CVE-2026-109513 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-109513 being exploited in the wild.
How severe is CVE-2026-109513?: High severity, with a CVSS score of 7.2, 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-109513?: 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-109513 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-109513?: 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

This is a stored cross-site scripting (XSS) vulnerability in the NotificationX WordPress plugin versions up to 3.3.3, affecting the 'name' parameter due to insufficient input sanitization and output escaping. Unauthenticated attackers can inject arbitrary JavaScript that persists in the database and executes in the browsers of all users who visit affected pages. The vulnerability requires prior admin configuration (WordPress.org Reviews campaign enabled and notificationx dynamic block deployed).

Affected products

NotificationX NotificationX up to and including 3.3.3

Timeline

2026-10-16: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.