CVE-2025-47602
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 ammarahmad786 Calculate Prices based on Distance For WooCommerce calculate-prices-based-on-distance-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Calculate Prices based on Distance For WooCommerce: from n/a through <= 1.3.5.
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 · low confidenceMissing authorization vulnerability in the Calculate Prices based on Distance For WooCommerce plugin allows attackers to access functionality that should require proper authentication and access control. The plugin fails to enforce authorization checks on certain endpoints or functions, potentially enabling unauthorized users to manipulate distance-based shipping calculations.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedCheck your WordPress installation for the Calculate Prices based on Distance For WooCommerce plugin in the wp-content/plugins directory or via the WordPress admin Plugins pageAffected if The plugin is found installed in the environment
-
Identify the installed versionLocate the main plugin file and read the version header (typically found in the plugin comments at the top of the main PHP file), or check the version displayed in the WordPress admin Plugins listAffected if The version number cannot be determined or is older than the patched release
-
Determine if the vulnerable endpoints are exposedIdentify the plugin AJAX handlers or REST API endpoints it registers (check plugin code for wp_ajax_ and wp_ajax_nopriv_ hooks, or REST route registrations). Test accessing these endpoints without authentication using a tool like curlAffected if The endpoints respond to unauthenticated requests and return expected functionality rather than requiring authentication
-
Check access control on admin functionsReview the plugin code to identify any functions that perform distance-based shipping calculations or price modifications. Test whether these can be invoked directly via URL without admin privilegesAffected if The functions execute without verifying user capabilities or session authentication
-
Inspect capability checksSearch the plugin source code for current_user_can, wp_get_current_user, or similar WordPress authorization functions around the vulnerable functions identified in the summaryAffected if No capability checks are found before distance calculation or price manipulation logic
The environment is affected if the plugin is installed and the installed version lacks the authorization fixes, particularly if the vulnerable endpoints are accessible without authentication.
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 if a patched release is available; otherwise, disable the plugin until a fix is released. Consider restricting access to vulnerable endpoints via web server configuration as a temporary measure.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47602 — 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-47602 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