dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-54802

HIGH · 7.5 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Unauthenticated Broken Authentication in SMS Alert Order Notifications <= 3.9.3 versions.

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

Unauthenticated broken authentication vulnerability in SMS Alert plugin allows unauthenticated attackers to access or manipulate order notification functions due to improper authentication controls in versions 3.9.3 and below.

MitigationUpdate SMS Alert plugin to version 3.9.4 or later to remediate the broken authentication vulnerability.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 if SMS Alert plugin is installed
    Locate the SMS Alert plugin files in the WordPress plugins directory (wp-content/plugins/sms-alert) or check via WordPress admin plugin list
    Affected if SMS Alert plugin is present in the installation
  2. Determine installed SMS Alert plugin version
    Check the plugin header in main PHP file (typically sms-alert/sms-alert.php) for 'Version:' field, or look in WordPress plugin admin page
    Affected if Version is 3.9.3 or below
  3. Verify order notification functions are exposed
    Test access to order notification endpoints (such as order creation/modification callbacks) without providing authentication credentials
    Affected if Order notification endpoints respond without requiring authentication (HTTP 200 instead of 401/403)
  4. Check for unauthorized access to notification settings
    Attempt to access SMS Alert notification configuration endpoints or AJAX actions without logged-in session
    Affected if Settings or notification functions are accessible to anonymous users

A user is affected if the SMS Alert plugin version is 3.9.3 or below and the order notification functions are accessible to unauthenticated users.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update SMS Alert plugin to version 3.9.4 or later to remediate the broken authentication vulnerability.

Recommended fix Moderate confidence

SMS Alert Order Notifications version 3.9.4 or latest available version

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'SMS Alert Order Notifications' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Verify the update was successful and the plugin is now running version 3.9.4 or higher
  6. 6. Test that order notification SMS functionality continues to work correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54802 — 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-54802 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