dbcve.org
Wooodt LiteWordPress extension · Byconsole

CVE-2023-47179

HIGH · 8.8 CVSS v3.1 Published 2025-01-02
Fix available
A fix is available. Upgrade to 2.4.7 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 mdalabar WooODT Lite byconsole-woo-order-delivery-time allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WooODT Lite: from n/a through <= 2.4.6.

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 WooODT Lite WordPress plugin allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthenticated or unauthorized users to perform actions that should be restricted to privileged users.

MitigationImplement proper authorization checks (capability checks and nonce verification) on all sensitive endpoints and actions within the plugin, and update to the latest patched version once available.

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.4.7

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 WooODT Lite plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WooODT Lite' or 'Byconsole Wooodt Lite' in the list. Alternatively, check if the directory wp-content/plugins/wooodt-lite/ or similar exists on the server.
    Affected if The plugin appears in the installed plugins list or the plugin directory exists on the server.
  2. Determine installed plugin version
    In WordPress admin > Plugins > Installed Plugins, click on the plugin name to view details and locate the version number. Alternatively, inspect the main plugin file (e.g., wooodt-lite.php) or readme.txt in the plugin directory for the 'Version:' header field.
    Affected if The displayed version number is lower than 2.4.7 (e.g., 2.4.6, 2.4.5, 1.x.x, etc.).
  3. Identify exposed sensitive endpoints
    Review the plugin directory for PHP files handling admin actions or AJAX endpoints. Common paths include wp-content/plugins/wooodt-lite/includes/ or admin/. Search for files containing 'add_action' with 'wp_ajax' or 'admin_action' hooks that process sensitive operations without current_user_can() or nonce verification checks.
    Affected if Sensitive action handlers exist in the plugin files without proper capability checks (current_user_can) and nonce verification (wp_verify_nonce) on the exposed endpoints.
  4. Test for unauthorized access
    If you have access to the site filesystem, inspect the plugin's PHP files for functions that handle order data, export operations, or user privilege modifications. Check if these functions verify user authentication and authorization before executing. Look for missing 'current_user_can' or 'is_user_logged_in' conditionals at the function entry points.
    Affected if Any sensitive function in the plugin executes without verifying the current user has appropriate privileges (administrator or shop_manager roles).

A user is affected if the WooODT Lite plugin is installed with a version lower than 2.4.7 and contains sensitive endpoints or actions that lack authorization verification.

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 2.4.7 or later
Fixed in 2.4.7
Interim mitigation

Implement proper authorization checks (capability checks and nonce verification) on all sensitive endpoints and actions within the plugin, and update to the latest patched version once available.

Recommended fix Moderate confidence

2.4.7

  1. Update the WooODT Lite plugin to version 2.4.7 or later
  2. After updating, verify that all order delivery time settings and access controls are functioning correctly
  3. Test that unauthorized users can no longer access administrative functions that should require authorization

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

Fix this in Wooodt Lite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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