dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-66109

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-21
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 Octolize Shipping Plugins Cart Weight for WooCommerce woo-cart-weight allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Cart Weight for WooCommerce: from n/a through <= 1.9.11.

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

This is a missing authorization vulnerability in the Cart Weight for WooCommerce plugin (woo-cart-weight) that allows unauthenticated or improperly authorized users to access functionality they should not have access to due to incorrectly configured access control security levels.

MitigationUpdate to the latest version of Cart Weight for WooCommerce once a patch is released. If no patch is available, review and restrict plugin admin capabilities and consider adding application-level access controls.

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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. Verify Cart Weight for WooCommerce is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Cart Weight for WooCommerce' or check the file wp-content/plugins/woo-cart-weight/woo-cart-weight.php for the plugin header version
    Affected if The plugin is installed and active
  2. Identify installed plugin version
    Open wp-content/plugins/woo-cart-weight/woo-cart-weight.php and locate the 'Version' header in the plugin comment block, or view the plugin details in WordPress admin Plugins page
    Affected if Version cannot be confirmed as the latest patched release (version comparison required against any advisory)
  3. Confirm WooCommerce is active
    In WordPress admin, verify WooCommerce is installed and active under Plugins; the vulnerability requires WooCommerce to be running as this is a WooCommerce extension
    Affected if WooCommerce is not active or not installed
  4. Check WordPress user roles and capabilities
    Navigate to Users > Roles (or use a role editor plugin) and review what roles have 'manage_options' or administrative capabilities assigned to the site
    Affected if Untrusted or low-privilege user roles exist with administrative access to plugin settings
  5. Audit admin access to plugin settings
    Attempt to access the plugin settings page (usually under WooCommerce > Cart Weight or similar) while logged in as a non-administrator user, or inspect the plugin admin menu registration in the code
    Affected if Non-administrator users can access or modify plugin configuration

User is affected if Cart Weight for WooCommerce plugin is installed and its settings or functionality can be accessed by users lacking proper authorization, particularly unauthenticated visitors or low-privilege 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of Cart Weight for WooCommerce once a patch is released. If no patch is available, review and restrict plugin admin capabilities and consider adding application-level access controls.

Recommended fix Moderate confidence

Cart Weight for WooCommerce version > 1.9.11 (latest stable release)

  1. 1. Verify the current installed version of Cart Weight for WooCommerce plugin in your WordPress/WooCommerce environment
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. Locate Cart Weight for WooCommerce (woo-cart-weight) in the plugins list
  4. 4. Check if the currently installed version is <= 1.9.11 (vulnerable)
  5. 5. If vulnerable, update the plugin to the latest available version from the WordPress plugin repository or from Octolize
  6. 6. After updating, verify the new version number reflects the fix (version > 1.9.11)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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