LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-0554 lets logged-in WordPress users with Contributor-level access or higher reset NotificationX campaign analytics they do not own. This affects data integrity, not confidentiality or site takeover. Business urgency is moderate where marketing, conversion, or campaign reporting relies on NotificationX analytics.

Executive priority

Treat as a moderate-priority integrity issue. It is unlikely to cause full compromise by itself, but it can damage campaign reporting and trust in marketing metrics on affected WordPress sites.

Technical view

NotificationX for WordPress lacks proper capability checks on the “regenerate” and “reset” REST API endpoints through version 3.1.11. Authenticated Contributor+ users can reset analytics for any NotificationX campaign. CVSS is 4.3 with low attack complexity and low privileges required; impact is limited to integrity.

Likely exposure

Exposure is limited to WordPress sites running NotificationX up to and including 3.1.11, especially sites allowing Contributor, Author, Editor, or Administrator accounts for multiple users.

Exploitation context

The vulnerability requires authentication and Contributor-level access or higher. The provided sources do not indicate CISA KEV listing or confirmed active exploitation. Abuse would primarily disrupt campaign analytics and reporting accuracy.

Researcher notes

Evidence supports CWE-862 missing authorization on two REST endpoints. Scope appears authenticated and Contributor+. The bundle does not provide exploit-in-the-wild evidence. The WordPress Trac changeset should be reviewed to confirm the exact fixed release and code-level remediation.

Mitigation direction

  • Check the installed NotificationX version on all WordPress sites.
  • Update NotificationX according to vendor or WordPress plugin repository guidance.
  • Limit Contributor-level access to trusted users only.
  • Review and remove unused WordPress accounts with content privileges.
  • Monitor NotificationX analytics for unexpected resets or gaps.

Validation and detection

  • Inventory WordPress sites using the NotificationX plugin.
  • Confirm whether installed versions are 3.1.11 or earlier.
  • Review user accounts with Contributor-level access or higher.
  • Check change logs or vendor notes for the authorization fix.
  • Review campaign analytics history for unexplained reset events.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0554 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-0554Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
wpdevteamNotificationX – FOMO, Live Sales Notification, WooCommerce Sales Popup, GDPR, Social Proof, Announcement Banner & Floating Notification Bar0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.