WordPress NotificationX Plugin Stored XSS via Name Parameter

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.

Casky was already ahead

This CVE exploits attack patterns that Casky's 323matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

This vulnerability is a Stored Cross-Site Scripting (XSS) flaw in the NotificationX WordPress plugin affecting all versions up to 3.3.3. The 'name' parameter fails to properly sanitize and escape user input, allowing unauthenticated attackers to inject malicious JavaScript that persists in the database. When any user visits a page containing the injected payload, the malicious script executes in their browser with their privileges. This poses significant risk to WordPress sites using this popular notification and FOMO plugin, as attackers can steal session cookies, capture credentials, redirect users to malicious sites, or deface content without requiring authentication or administrative access.

Casky's 323 mapped security skills leverage Claude AI's extended reasoning to detect attack patterns associated with techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky would observe detection findings focused on: (1) unusual input patterns in notification name fields containing script tags or event handlers; (2) database-level monitoring identifying stored payloads that trigger on page render; (3) behavioral analysis of unauthenticated requests attempting parameter injection; and (4) output encoding gaps where untrusted data flows directly to DOM rendering without escaping. The platform would surface these anomalies alongside MITRE ATT&CK context, enabling teams to correlate stored XSS attempts with broader reconnaissance activities and initial access chains targeting their WordPress infrastructure.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

323 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-109513.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-109513

Casky has 323 skills that investigate the attack patterns behind CVE-2026-109513. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn