CVE-2025-26764
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 · uneditedMissing 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 confidenceThe Distance Based Shipping Calculator WordPress plugin has a missing authorization vulnerability allowing authenticated users to exploit incorrectly configured access control security levels. This broken access control issue enables users with low privileges to access functionality intended for higher-privileged users.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Distance Based Shipping Calculator', or check the /wp-content/plugins/ directory for the plugin folderAffected if The plugin is installed and active
-
Check the installed versionIn WordPress admin Plugins list, find the Distance Based Shipping Calculator entry and note the version number displayed, or read the main plugin file header for the Version fieldAffected if The version is older than the latest available version (indicating unpatched code)
-
Identify user roles with access to shipping settingsIn WordPress admin, go to the plugin settings page for Distance Based Shipping Calculator and review which user roles (Administrator, Editor, Author, Contributor, Subscriber) are permitted to modify shipping calculations or ratesAffected if Low-privilege roles such as Subscriber, Contributor, or Author have access to shipping configuration functions
-
Test authorization on plugin endpointsUsing a low-privilege user account (e.g., Subscriber), attempt to access or modify shipping calculation settings, submit requests to plugin AJAX endpoints, or call functions that should be restricted to administratorsAffected if Low-privilege users can successfully access or modify shipping settings that should require administrator privileges
A user is affected if the Distance Based Shipping Calculator plugin is installed, the installed version is older than the latest release, and low-privilege WordPress users can access shipping configuration functions intended only for administrators
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to the latest version once available, or implement proper authorization checks on all sensitive endpoints/functions within the plugin.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-26764 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26764 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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