CVE-2026-0554

NotificationX <= 3.1.11 - Missing Authorization to Authenticated (Contributor+) Analytics Reset

2026-01-20 01:50
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 3.2.1
Affected Plugin
NotificationX – FOMO, Live Sales Notification, WooCommerce Sales Popup, GDPR, Social Proof, Announcement Banner & Floating Notification Bar
Affected Version
<= 3.1.11
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-0554
View all NotificationX – FOMO, Live Sales Notification, WooCommerce Sales Popup, GDPR, Social Proof, Announcement Banner & Floating Notification Bar vulnerabilities

At a glance

CVE-2026-0554 is a medium-severity Missing Authorization vulnerability in the NotificationX WordPress plugin, affecting versions <= 3.1.11. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.2.1; sites on affected versions should update now. Disclosed January 2026, reported by Dmitrii Ignatyev.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

NotificationX <= 3.1.11 carries this weakness at regenerate, and reaching it takes an account at Contributor level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For NotificationX the fix is 3.2.1: builds <= 3.1.11 are affected, anything from 3.2.1 onward is not.

Remediation

Update to version 3.2.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: NotificationX 3.2.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-0554https://www.wordfence.com/threat-intel/vulnerabilities/id/e3cd843b-ab38-45c4-a661-78d4e6db5201https://nvd.nist.gov/vuln/detail/CVE-2026-0554

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C