dbcve.org
DocketWordPress extension · Wpwebelite

CVE-2024-43131

HIGH · 7.5 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 1.7.0 or later.
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
Incorrect Authorization vulnerability in WPWeb Docket (WooCommerce Collections / Wishlist / Watchlist) allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Docket (WooCommerce Collections / Wishlist / Watchlist): from n/a before 1.7.0.

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

The WPWeb Docket WordPress plugin (WooCommerce Collections/Wishlist/Watchlist) has an incorrect authorization vulnerability allowing users to access functionality that should be constrained by access control lists (ACLs). This authorization bypass likely enables unauthorized viewing, modification, or deletion of other users' collections, wishlists, or watchlists.

MitigationUpdate the Docket plugin to version 1.7.0 or later to patch the authorization bypass vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DocketWordPress extension
Affected:< 1.7.0= 1.7.0

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Check installed Docket plugin version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, locate 'WPWeb Elite Docket' or 'Docket' plugin, and note the version number displayed
    Affected if The installed version is less than 1.7.0 or exactly equals 1.7.0
  2. Verify plugin is active with collections feature
    In WordPress admin, confirm the Docket plugin is activated and that WooCommerce Collections/Wishlist/Watchlist functionality is enabled for users
    Affected if The plugin is active and the collections/wishlist/watchlist feature is enabled, exposing the authorization bypass
  3. Inspect user collection access patterns
    Review WordPress user access logs or attempt to access collection endpoints (typically /docket/collections/) as a lower-privileged user to verify ACL enforcement
    Affected if Users can view, modify, or delete collections belonging to other users without proper authorization checks

A user is affected if the Docket plugin version is 1.7.0 or lower and the collections/wishlist/watchlist feature is active, allowing unauthorized access to other users' data.

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
Upgrade available Upgrade to 1.7.0 or later
Fixed in 1.7.0
Interim mitigation

Update the Docket plugin to version 1.7.0 or later to patch the authorization bypass vulnerability.

Recommended fix Moderate confidence

1.7.0 or later (latest available version)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Docket (WooCommerce Collections / Wishlist / Watchlist)' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository or WPWeb's official site and upload it manually
  6. 6. After updating, clear any caching mechanisms and verify the plugin is functioning correctly

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

Fix this in Docket Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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