---
id: "CVE-2026-109513"
kind: "vulnerability"
aliases: ["CVE-2026-109513"]
title: "NotificationX WordPress plugin: unauthenticated stored XSS via name parameter"
severity: "high"
cvss: 7.2
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["notificationx", "package", "self-hosted", "wordpress", "wordpress-plugin"]
not_affected_if: ["default-config", "no-public-notificationx-block"]
published_at: "2026-10-16T06:17:08+00:00"
first_seen_at: "2026-10-23T21:57:12+00:00"
updated_at: "2026-10-25T03:29:49+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-109513", "first_seen_at": "2026-10-23T21:57:12+00:00"}]
---

# NotificationX WordPress plugin: unauthenticated stored XSS via name parameter

The NotificationX WordPress plugin up to and including 3.3.3 does not sanitize the 'name' parameter, so unauthenticated attackers can store script that runs in visitors' browsers on pages showing the notification block. The injected script runs whenever a user loads an affected public page.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed NotificationX version in the WordPress plugins screen or with `wp plugin get notificationx --field=version`
- Confirm whether the WordPress.org Reviews campaign is enabled and the notificationx dynamic block is placed on a public page (unknown if sources give a specific location)

## Fix

- Update NotificationX to a version later than `3.3.3` (the first fixed version is unknown from the sources)
- Until updated, disable the WordPress.org Reviews campaign or remove the notificationx block from public pages

## Timeline

- 2026-10-23T21:57:12+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-109513

## From the sources

The NotificationX – FOMO, Live Sales Notification, WooCommerce Sales Popup, GDPR, Social Proof, Announcement Banner & Floating Notification Bar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'name' parameter in all versions up to, and including, 3.3.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires that an administrator has previously enabled a WordPress.org Reviews campaign and placed the notificationx-pro/notificationx dynamic block on a public page, both of which are documented, supported plugin workflows.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_