dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-38702

MEDIUM · 5.3 CVSS v3.1 Published 2024-11-01
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 Tyche Softwares Product Delivery Date for WooCommerce – Lite allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Product Delivery Date for WooCommerce – Lite: from n/a through 2.7.2.

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 Product Delivery Date for WooCommerce – Lite WordPress plugin (versions through 2.7.2) allows users to access functionality that should be constrained by access control lists. This is a broken access control issue where certain administrative or privileged functions can be reached without proper permission checks.

MitigationUpdate to the latest version of the plugin if a patched release is available; otherwise, restrict access to the plugin's admin functionality via server-level authentication or disable the plugin until a fix is released.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Confirm the plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Product Delivery Date for WooCommerce - Lite', or inspect the directory wp-content/plugins/ for a folder containing 'product-delivery-date-for-woocommerce-lite'
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed for 'Product Delivery Date for WooCommerce - Lite', or open the main plugin file (usually named like pwcd-lite.php or similar) and read the 'Version:' header in the plugin comments
    Affected if The version displayed is 2.7.2 or any version number lower than 2.7.2
  3. Verify administrative functions are exposed
    Attempt to access the plugin's admin pages (typically under /wp-admin/admin.php?page=product_delivery_date or similar) while logged in as a low-privilege user (subscriber or customer role) who should not have administrative access
    Affected if The administrative interface loads or responds without rejecting the user due to insufficient privileges
  4. Test for broken access control on delivery date features
    Using a non-administrator account, submit a delivery date order request or modify delivery settings via the plugin functionality that should be restricted to administrators
    Affected if The action completes successfully without an authorization error or access denied message

A user is affected if the plugin is installed with version 2.7.2 or lower and low-privilege users can access administrative features or modify delivery settings without proper authorization checks.

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 the plugin if a patched release is available; otherwise, restrict access to the plugin's admin functionality via server-level authentication or disable the plugin until a fix is released.

Recommended fix High confidence

2.7.3

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the plugin 'Product Delivery Date for WooCommerce – Lite'
  4. 4. Check the currently installed version (vulnerable if 2.7.2 or lower)
  5. 5. If an update is available, click 'Update Now' to upgrade to version 2.7.3
  6. 6. Alternatively, manually download version 2.7.3 from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the new version number in the plugins list

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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