dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-27042

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Missing authorization vulnerability in the NotificationX WordPress plugin allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly verify user permissions before allowing access to certain functionality, potentially permitting unauthorized actions.

MitigationUpdate NotificationX to a version beyond 3.2.1 once available, or implement proper authorization checks on affected plugin functions. If no patch is available, restrict access to the plugin admin pages via server-level access controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check NotificationX plugin version
    In WordPress admin, go to Plugins > Installed Plugins > locate NotificationX and read the version number from the plugin description. Alternatively, check the main plugin file (usually wp-content/plugins/notificationx/includes/notificationx.php) for the 'Version' header comment.
    Affected if Installed version is 3.2.1 or earlier (versions beyond 3.2.1 are patched)
  2. Verify NotificationX plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm the NotificationX plugin has the 'Active' status indicator.
    Affected if Plugin is active and running a vulnerable version
  3. Check user role capability settings
    Navigate to NotificationX > Settings > General tab and examine the 'Who Can View' or similar permission-related options that control access levels.
    Affected if Settings allow lower-privileged users (like Editors or Authors) to access plugin functionality that should be restricted to Administrators
  4. Inspect admin access controls
    Access NotificationX admin pages (NotificationX > All Notifications, NotificationX > Settings) and verify which user roles can view/modify these pages.
    Affected if Non-administrator users can access NotificationX admin functionality without proper capability checks

Environment is affected if NotificationX plugin version 3.2.1 or earlier is installed and active, with permission settings that allow non-administrator users to access plugin features.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update NotificationX to a version beyond 3.2.1 once available, or implement proper authorization checks on affected plugin functions. If no patch is available, restrict access to the plugin admin pages via server-level access controls.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27042 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27042 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data