dbcve.org
Wooodt LiteWordPress extension · Byconsole

CVE-2024-13540

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-18
Fix available
A fix is available. Upgrade to after 2.5.1 or later.
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
The WooODT Lite – Delivery & pickup date time location for WooCommerce plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 2.5.1. This is due the /inc/bycwooodt_get_all_orders.php file being publicly accessible and generating a publicly visible error message. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.

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 · high confidence

The WooODT Lite WordPress plugin has a publicly accessible PHP file (/inc/bycwooodt_get_all_orders.php) that outputs an error message revealing the full server path to the web application. Unauthenticated attackers can access this file directly to obtain the absolute filesystem path.

MitigationRestrict direct access to the /inc/bycwooodt_get_all_orders.php file, or disable PHP error display in production environments. Alternatively, remove or relocate the file if unused.

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
Wooodt LiteWordPress extension
Affected:<= 2.5.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 the Byconsole Wooodt Lite plugin is installed
    Check your WordPress plugins directory or wp-admin for the Byconsole Wooodt Lite plugin and note its installed version
    Affected if The plugin is installed and the version is 2.5.1 or lower
  2. Confirm the vulnerable file exists in the plugin directory
    Locate the file at /wp-content/plugins/byconsole-wooodt-lite/inc/bycwooodt_get_all_orders.php (path may vary based on installation)
    Affected if The file exists in the plugin directory
  3. Test direct access to the vulnerable file
    Using a web browser or curl, make a GET request to the file URL: https://yourdomain.com/wp-content/plugins/byconsole-wooodt-lite/inc/bycwooodt_get_all_orders.php
    Affected if The request returns an error message that exposes the absolute filesystem path (e.g., /var/www/html/...)

If the Byconsole Wooodt Lite plugin version is 2.5.1 or lower AND the /inc/bycwooodt_get_all_orders.php file is directly accessible and outputs the server path, the environment is affected by this CVE.

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 a release after 2.5.1
Interim mitigation

Restrict direct access to the /inc/bycwooodt_get_all_orders.php file, or disable PHP error display in production environments. Alternatively, remove or relocate the file if unused.

Recommended fix Moderate confidence

Latest available version (check WordPress plugin repository for version newer than 2.5.1)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the WooODT Lite plugin
  4. Check if an update is available and update to the latest version
  5. Alternatively, download the latest version from the WordPress plugin repository and reinstall

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

Fix this in Wooodt Lite Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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