dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14948

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-10
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
The miniOrange OTP Verification and SMS Notification for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the `enable_wc_sms_notification` AJAX action in all versions up to, and including, 4.3.8. This makes it possible for unauthenticated attackers to enable or disable SMS notification settings for WooCommerce orders.

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 · high confidence

The miniOrange OTP Verification and SMS Notification plugin for WooCommerce has a broken access control vulnerability. The AJAX action `enable_wc_sms_notification` lacks a capability check, allowing any unauthenticated user to enable or disable SMS notification settings for WooCommerce orders. This is an Insecure Direct Object Reference (IDOR) issue where the server trusts client-provided input without proper authorization verification.

MitigationUpdate the plugin to the latest version to receive the patched code that adds proper capability checks and nonce validation to the affected AJAX action. Until patched, monitor for unauthorized changes to SMS notification settings.

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. Confirm miniOrange OTP plugin is installed
    Navigate to WordPress admin > Plugins and look for 'miniOrange OTP Verification and SMS Notification' or check the plugins directory for the miniorange-otp-verification folder
    Affected if The plugin is installed and active
  2. Identify the plugin version
    In WordPress admin > Plugins, click on the plugin to view details and note the installed version number
    Affected if Version cannot be determined or is unknown (treat as potentially vulnerable since no patched version is specified)
  3. Verify AJAX endpoint accessibility
    Check if the WordPress AJAX endpoint /wp-admin/admin-ajax.php responds to the 'enable_wc_sms_notification' action without requiring authentication - attempt a test request or inspect the plugin source code for the action handler
    Affected if The AJAX action 'enable_wc_sms_notification' is registered and accessible without capability checks
  4. Inspect SMS notification configuration
    In WooCommerce > Settings > SMS Notifications, review the current settings for any unauthorized or unexpected changes to notification preferences
    Affected if SMS notification settings have been modified without admin authorization
  5. Review access logs for suspicious AJAX calls
    Examine web server access logs for POST requests to admin-ajax.php with action parameter 'enable_wc_sms_notification' originating from unauthenticated IP addresses
    Affected if Unauthenticated requests to enable_wc_sms_notification are present in logs

A user is affected if the miniOrange OTP Verification and SMS Notification plugin is installed and the enable_wc_sms_notification AJAX action can be invoked without authentication to modify SMS settings.

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 the plugin to the latest version to receive the patched code that adds proper capability checks and nonce validation to the affected AJAX action. Until patched, monitor for unauthorized changes to SMS notification settings.

Recommended fix Moderate confidence

Plugin version 4.3.9 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'miniOrange OTP Verification and SMS Notification for WooCommerce' plugin
  4. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org/plugins
  5. Verify the updated version is 4.3.9 or higher
  6. Test that the SMS notification settings can only be modified by authenticated users with appropriate capabilities

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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