Skip to content
Laskyr

Plugins · notificationx · data as of 2026-11-04

Is NotificationX safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (3.3.7)

As of 2026-11-04. 10 issues are on record for older versions; version 3.3.4 or newer fixes all of them that state a fix.

Latest version
3.3.7
Last updated
2026-11-02
Active installs
30,000+
Known issues on record
10
Unpatched in latest
0
Tested up to WP
7.1.4 · PHP 5.6+

Want to boost business trust & conversions? 97% of visitors hesitate to buy because of credibility. Instantly succeed with WooCommerce Sales Alert! — by WPDeveloper

What to do

  1. Update to the latest version (3.3.7). Anything older than 3.3.4 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
  2. If you cannot update right away, deactivate it until you can.
  3. Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
  4. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get notificationx --field=version shows what you run; wp plugin update notificationx updates it.

Check your version

Known vulnerabilities

10 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

high 7.2 CVE-2026-109513 · published 2026-10-16

Stored cross-site scripting (XSS) in NotificationX (3.3.3 and older)

Affected
3.3.3 and older
Fixed in
3.3.4 *
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

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.

NVD CVE-2026-109513Wordfence advisoryCode change (fix)Plugin source

medium 5.3 CVE-2026-110721 · published 2026-10-16

Missing authorization check in NotificationX (3.3.3 and older)

Affected
3.3.3 and older
Fixed in
3.3.4 *
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The NotificationX plugin for WordPress is vulnerable to Missing Authorization leading to arbitrary content injection in versions up to, and including, 3.3.3 The /notificationx/v1/popup-submit REST route is registered with permission_callback => '__return_true', and the handler at PopupNotification::handle_popup_submission() 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 (the two sources this form is intended to serve). This makes it possible for unauthenticated attackers to inject forged social-proof entries (name, title, message, email, theme) into any enabled non-popup NotificationX campaign — WP Comments, WooCommerce/EDD/Give sales, reviews, etc.

NVD CVE-2026-110721Wordfence advisoryCode change (fix)Plugin source

medium 5.3 CVE-2026-27042 · published 2026-02-19

Missing authorization check in NotificationX (3.2.1 and older)

Affected
3.2.1 and older
Fixed in
3.2.2
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Patchstack
Details from the advisory

Missing Authorization vulnerability in WPDeveloper NotificationX notificationx allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects NotificationX: from n/a through <= 3.2.1.

NVD CVE-2026-27042Patchstack advisory

medium 4.3 CVE-2026-0554 · published 2026-01-20

Missing authorization check in NotificationX (3.1.11 and older)

Affected
3.1.11 and older
Fixed in
3.2.0 *
Access needed (per CVSS)
Needs a low-level account (e.g. subscriber)
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The NotificationX plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'regenerate' and 'reset' REST API endpoints in all versions up to, and including, 3.1.11. This makes it possible for authenticated attackers, with Contributor-level access and above, to reset analytics for any NotificationX campaign, regardless of ownership.

NVD CVE-2026-0554Wordfence advisoryCode change (fix)research.cleantalk.org

high 7.2 CVE-2025-15380 · published 2026-01-20

DOM-based cross-site scripting (XSS) in NotificationX (3.2.0 and older)

Affected
3.2.0 and older
Fixed in
3.2.1 *
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The NotificationX – FOMO, Live Sales Notification, WooCommerce Sales Popup, GDPR, Social Proof, Announcement Banner & Floating Notification Bar plugin for WordPress is vulnerable to DOM-Based Cross-Site Scripting via the 'nx-preview' POST parameter in all versions up to, and including, 3.2.0. This is due to insufficient input sanitization and output escaping when processing preview data. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute when a user visits a malicious page that auto-submits a form to the vulnerable site.

NVD CVE-2025-15380Wordfence advisoryCode change (fix)research.cleantalk.org

medium 5.4 CVE-2025-22683 · published 2025-02-03

Stored cross-site scripting (XSS) in NotificationX (2.9.5 and older)

Affected
2.9.5 and older
Fixed in
3.0.0
Access needed (per CVSS)
Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from
CVE record (the advisory publisher) · score by NVD
Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WPDeveloper NotificationX notificationx allows Stored XSS.This issue affects NotificationX: from n/a through <= 2.9.5.

NVD CVE-2025-22683Patchstack advisory

medium 4.4 CVE-2024-11727 · published 2024-12-12

Stored cross-site scripting (XSS) in NotificationX (2.9.3 and older)

Affected
2.9.3 and older
Fixed in
2.9.4 *
Access needed (per CVSS)
Needs an admin-level account
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The NotificationX – Live Sales Notification, WooCommerce Sales Popup, FOMO, Social Proof, Announcement Banner & Floating Notification Top Bar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's content settings for notifications in all versions up to, and including, 2.9.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

NVD CVE-2024-11727Wordfence advisoryCode change (fix)

critical 9.8 CVE-2024-1698 · published 2024-02-27

SQL injection in NotificationX (2.8.2 and older)

Affected
2.8.2 and older
Fixed in
2.8.3 *
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by NVD
Details from the advisory

The NotificationX – Best FOMO, Social Proof, WooCommerce Sales Popup & Notification Bar Plugin With Elementor plugin for WordPress is vulnerable to SQL Injection via the 'type' parameter in all versions up to, and including, 2.8.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

NVD CVE-2024-1698Wordfence advisoryCode change (fix)vicarius.io

medium 4.3 CVE-2020-36744 · published 2023-07-01

Cross-site request forgery (CSRF) in NotificationX (older than 1.8.3)

Affected
older than 1.8.3
Fixed in
1.8.3
Access needed (per CVSS)
No login needed; someone on the site has to click a link or open a page
Range from
CVE record (the advisory publisher) · score by NVD
Details from the advisory

The NotificationX plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.8.2. This is due to missing or incorrect nonce validation on the generate_conversions() function. This makes it possible for unauthenticated attackers to generate conversions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

NVD CVE-2020-36744Wordfence advisoryCode change (fix)blog.nintechnet.comblog.nintechnet.comblog.nintechnet.comblog.nintechnet.com

critical 9.8 CVE-2022-0349 · published 2022-03-07

SQL injection in NotificationX (older than 2.3.9)

Affected
older than 2.3.9
Fixed in
2.3.9
Access needed (per CVSS)
No login needed
Range from
NVD analysis · score by NVD
Details from the advisory

The NotificationX WordPress plugin before 2.3.9 does not sanitise and escape the nx_id parameter before using it in a SQL statement, leading to an Unauthenticated Blind SQL Injection

NVD CVE-2022-0349WPScan advisory

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
NotificationX vulnerability status badge
<a href="https://laskyr.com/plugins/notificationx"><img src="https://laskyr.com/plugins/notificationx/badge.svg" alt="NotificationX vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit