dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-26765

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-16
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 enituretechnology Distance Based Shipping Calculator distance-based-shipping-calculator allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Distance Based Shipping Calculator: from n/a through <= 2.0.22.

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 the Distance Based Shipping Calculator WordPress plugin allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly validate user permissions before allowing access to shipping calculation functions, potentially permitting authenticated users with limited privileges to access or manipulate shipping-related features intended for administrators.

MitigationUpdate to version 2.0.23 or later which contains proper authorization controls. Until then, restrict plugin access to trusted administrator accounts only and monitor for suspicious shipping configuration changes.

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. Verify plugin is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'Distance Based Shipping Calculator' in the list. Confirm the plugin is currently active.
    Affected if The plugin is installed and active in WordPress.
  2. Check installed version
    In the Plugins list, find the Distance Based Shipping Calculator entry. The version number is displayed below the plugin name. Compare this version to the fixed release 2.0.23.
    Affected if The installed version is lower than 2.0.23.
  3. Check user registration settings
    Navigate to WordPress Settings > General and locate 'Membership' settings. Verify whether the option 'Anyone can register' is enabled and what default role is assigned to new users.
    Affected if Anyone can register is enabled, creating authenticated users with limited privileges who could potentially exploit the flaw.
  4. Review user roles with access
    Navigate to Users > All Users in WordPress admin. Identify accounts with roles other than Administrator (such as Editor, Author, Contributor, or Subscriber) that exist on the site.
    Affected if Non-administrator user accounts exist on the site, which could exploit the missing authorization if the vulnerable functionality is accessible to them.
  5. Inspect plugin authorization logic
    If you have file system access, locate the main plugin file (typically in wp-content/plugins/distance-based-shipping-calculator/) and review PHP files for capability checks. Look for functions handling shipping calculations or settings that lack current_user_can() or similar authorization checks.
    Affected if Plugin code lacks proper permission checks before executing shipping-related functions.

You are affected if the Distance Based Shipping Calculator plugin is installed with a version lower than 2.0.23 and your site allows non-administrator user accounts to exist, as these users could access restricted shipping features without proper authorization.

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 to version 2.0.23 or later which contains proper authorization controls. Until then, restrict plugin access to trusted administrator accounts only and monitor for suspicious shipping configuration changes.

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-26765 — 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-26765 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