dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-62006

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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 VeronaLabs WP SMS wp-sms.This issue affects WP SMS: from n/a through <= 7.0.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 VeronaLabs WP SMS WordPress plugin version <= 7.0.1 allows attackers to perform actions without proper permission verification. The specific impacted functions are not detailed, but authorization bypass typically enables unauthenticated or low-privilege users to access sensitive SMS sending capabilities or subscriber management features.

MitigationImplement proper capability checks (e.g., current_user_can()) and nonce validation on all AJAX handlers and admin pages within the plugin. Restrict SMS sending and subscriber management functions to users with appropriate WordPress roles.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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 the installed version of WP SMS plugin
    In WordPress admin, go to Plugins > Installed Plugins and find 'WP SMS' in the list, then look at the version number displayed. Alternatively, open the main plugin file (wp-sms.php or similar in /wp-content/plugins/wp-sms/) and locate the 'Version' header in the plugin comment block.
    Affected if The version listed is 7.0.1 or lower.
  2. Inspect AJAX handler registrations for missing capability checks
    Open the main plugin PHP files and search for 'add_action' calls registering AJAX actions (look for 'wp_ajax_' and 'wp_ajax_nopriv_' prefixes). Examine each registered callback function to see if it calls 'current_user_can()' or similar authorization function before executing sensitive operations.
    Affected if AJAX handlers are registered with 'wp_ajax_nopriv_' prefix, or handlers do not contain capability verification before processing requests.
  3. Review SMS sending functions for authorization
    Search the plugin source code for functions related to sending SMS (keywords: 'send_sms', 'sendMessage', 'wp_sms_send'). Open these functions and verify they include proper authorization checks such as 'current_user_can()' with appropriate capability strings (e.g., 'manage_options' or 'manage_sms').
    Affected if SMS sending functions execute without verifying user capabilities or permissions first.
  4. Examine subscriber management functions for access control
    Search the plugin code for functions handling subscriber lists (keywords: 'subscribe', 'unsubscribe', 'subscriber', 'add_user' to the SMS list). Check if these functions verify user permissions before allowing addition, removal, or export of subscriber data.
    Affected if Subscriber management operations can be triggered without authentication or proper capability verification.
  5. Check admin page registrations for proper protection
    Locate where the plugin adds admin menu items (search for 'add_menu_page', 'add_submenu_page', 'add_plugins_page'). Identify the callback functions for these admin pages and verify they include authentication and capability checks at the function entry point.
    Affected if Admin pages are accessible to users without verifying they have the 'manage_options' capability or equivalent.

A user is affected if they have WP SMS plugin version 7.0.1 or lower installed, or if the plugin's AJAX endpoints, SMS sending functions, or subscriber management features lack capability verification checks.

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

Implement proper capability checks (e.g., current_user_can()) and nonce validation on all AJAX handlers and admin pages within the plugin. Restrict SMS sending and subscriber management functions to users with appropriate WordPress roles.

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-2025-62006 — 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-62006 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