dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-62976

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-27
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 Joovii Sendle Shipping official-sendle-shipping-method allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Sendle Shipping: from n/a through <= 6.02.

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 check in the Joovii Sendle Shipping plugin for WooCommerce allows unauthenticated or unauthorized users to access certain functionality that should be restricted by Access Control Lists (ACLs). The vulnerability exists in versions through 6.02, where specific functions or endpoints lack proper capability checks or authentication validation before executing sensitive operations.

MitigationImplement proper authorization checks (capability checks, nonce verification, or user authentication validation) on all sensitive functions and admin-facing endpoints in the Sendle Shipping plugin. Restrict access to administrative functionality to only authorized users with appropriate WordPress capabilities.

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
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Locate the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Joovii Sendle Shipping. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file (usually in /wp-content/plugins/joovii-sendle-shipping/) for the 'Version' header in the file comment block.
    Affected if The version listed is 6.02 or any lower version number.
  2. Identify the plugin's PHP entry points
    Examine the plugin directory (/wp-content/plugins/joovii-sendle-shipping/) for PHP files containing AJAX handlers (search for 'add_action' with 'wp_ajax_' or 'wp_ajax_nopriv_'), admin menu registrations, or REST API endpoint registrations.
    Affected if The plugin exposes AJAX handlers, admin pages, or REST endpoints without visible capability checks.
  3. Inspect sensitive functions for capability checks
    Open the main plugin PHP file(s) and search for sensitive functions (order processing, shipping label generation, rate calculation, settings updates). Verify each contains a call to 'current_user_can()' or 'is_user_logged_in()' before executing the operation.
    Affected if Any sensitive function executes without first verifying user capabilities or authentication.
  4. Check AJAX endpoints for nopriv access
    Search the plugin code for 'wp_ajax_nopriv_' action hooks. These allow unauthenticated users to trigger specific functions. Review what those functions do and whether they perform their own authorization checks internally.
    Affected if The plugin registers wp_ajax_nopriv_ handlers that perform sensitive operations without internal authorization validation.
  5. Review admin page access controls
    Check for 'add_menu_page' or 'add_submenu_page' calls. Verify that associated page render functions or form handlers include 'current_user_can()' checks for capabilities like 'manage_options' or 'edit_products'.
    Affected if Admin pages or their form handlers lack capability verification before allowing configuration changes.

You are affected if the installed plugin version is 6.02 or lower and any sensitive functions, AJAX endpoints, or admin pages lack proper capability checks or authentication validation before executing operations.

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 authorization checks (capability checks, nonce verification, or user authentication validation) on all sensitive functions and admin-facing endpoints in the Sendle Shipping plugin. Restrict access to administrative functionality to only authorized users with appropriate WordPress capabilities.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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