CVE-2026-0554 MEDIUM

CVE-2026-0554: NotificationX <= 3.1.11 - Missing Authorization to Authenticated (Contributor+) Analytics Reset

Vendor Wpdevteam
Product NotificationX – FOMO, Live Sales Notification, WooCommerce Sales Popup, GDPR, Social Proof, Announcement Banner & Floating Notification Bar
Weakness CWE-862 · Missing authorization
Published January 20, 2026
Last update April 8, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

NotificationX versions up to 3.1.11 lack proper authorization checks, allowing authenticated users with low privileges to modify plugin settings and data. An attacker with a basic user account can change notification content, GDPR settings, or other configuration without permission. This affects the integrity of notifications and site compliance features but does not expose sensitive data or cause downtime.

What an attacker can do

03Attacker Capabilities

Modify NotificationX settings and notification content with a low-privilege user account.

Potential impact on your site

04Site Impact

Unauthorized users can alter FOMO notifications, sales popups, GDPR banners, and other plugin settings, potentially misleading visitors or breaking compliance.

Conditions required to exploit

05Prerequisites

Attacker needs a valid WordPress user account with low privileges (e.g., subscriber or contributor role).

Key dates

06Disclosure timeline

January 20, 2026 CVE published
April 8, 2026 Record updated