dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-25401

HIGH · 7.5 CVSS v3.1 Published 2026-03-25
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
Missing Authorization vulnerability in Arni Cinco WPCargo Track & Trace wpcargo allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WPCargo Track & Trace: from n/a through <= 8.0.2.

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 WPCargo Track & Trace WordPress plugin through version 8.0.2 contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels, potentially allowing unauthenticated or unauthorized users to access sensitive functionality or data.

MitigationUpdate WPCargo Track & Trace to the latest version once the patch is released. Until then, restrict access at the web server level or implement additional access control measures to limit exposure.

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. Identify if WPCargo plugin is installed
    Navigate to WordPress admin > Plugins, or check the /wp-content/plugins/ directory for the 'wpcargo' folder. Alternatively, query the wp_options table for option_name = 'active_plugins' or search for 'wpcargo' in the filesystem.
    Affected if The WPCargo plugin folder exists in the WordPress installation.
  2. Determine the installed WPCargo version
    In WordPress admin, go to Plugins > Installed Plugins > WPCargo Track & Trace and read the version number displayed. Alternatively, check the main plugin file (usually wp-content/plugins/wpcargo/wpcargo.php) for the 'Version' header in the plugin comment block.
    Affected if The installed version is 8.0.2 or any earlier version.
  3. Verify if the plugin REST API endpoints are publicly accessible
    Test common WPCargo REST API endpoints by sending a GET request without authentication credentials. Common endpoints include /wp-json/wpcargo/v1/ or similar paths under /wp-json/. Check for HTTP 200 responses that return data rather than 401/403 errors.
    Affected if The API endpoints respond with HTTP 200 and return shipment data without requiring authentication.
  4. Check for exposed shipment tracking functionality
    Access the WPCargo tracking page on the frontend (usually at /track-your-shipment/ or similar) and attempt to access or modify shipment information using only the tracking number, without any session or API key.
    Affected if Shipment details, status updates, or other sensitive data can be accessed or modified without authentication.
  5. Review WordPress user role permissions for WPCargo capabilities
    If the WordPress REST API returns 401 but the frontend tracking works without login, inspect the plugin's capability requirements in the code or test with a non-authenticated browser session to confirm access control gaps.
    Affected if Unauthenticated users can access or manipulate shipment data that should require elevated privileges.

Your environment is affected if the WPCargo Track & Trace plugin version is 8.0.2 or earlier AND the plugin's tracking endpoints or API 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.

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

Update WPCargo Track & Trace to the latest version once the patch is released. Until then, restrict access at the web server level or implement additional access control measures to limit exposure.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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