CVE-2026-27042
Missing Authorization in NotificationX Plugin Allows Unauthorized Access
Publication date: 2026-02-19
Last updated on: 2026-02-19
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wpdeveloper | notificationx | to 3.2.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-27042 is a Broken Access Control vulnerability in the WordPress NotificationX Plugin versions up to and including 3.2.1. It occurs due to missing authorization, authentication, or nonce token checks in certain functions, which allows unauthenticated users to perform actions that normally require higher privileges.
This means that users who are not logged in or do not have the necessary permissions can exploit this flaw to access or manipulate features they should not be able to.
How can this vulnerability impact me? :
The vulnerability allows unauthenticated users to perform privileged actions within the NotificationX plugin, potentially leading to unauthorized changes or access.
However, the severity is considered low with a CVSS score of 5.3, and it is unlikely to be exploited or pose a significant threat.
To mitigate the risk, users should update the plugin to version 3.2.2 or later, where the issue is fixed.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability arises from missing authorization and authentication checks in the NotificationX WordPress plugin up to version 3.2.1, allowing unauthenticated users to perform privileged actions.
Detection would involve checking the version of the NotificationX plugin installed on your WordPress site to see if it is version 3.2.1 or earlier.
Since the vulnerability can be triggered without authentication, monitoring for unusual or unauthorized actions related to NotificationX plugin features could also help detect exploitation attempts.
Specific commands to detect the vulnerability are not provided in the available resources.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to update the NotificationX WordPress plugin to version 3.2.2 or later, where the vulnerability is resolved.
Alternatively, applying patches or using auto-update solutions provided by Patchstack can help mitigate the risk.
Since the vulnerability requires no privileges to exploit, immediate updating is strongly recommended to prevent unauthorized access.