dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-42386

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Unauthenticated SQL Injection in Order Delivery Date for WooCommerce <= 4.5.1 versions.

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

Unauthenticated SQL Injection vulnerability in the Order Delivery Date plugin for WooCommerce versions 4.5.1 and below allows remote attackers to inject arbitrary SQL queries via unsanitized input parameters without requiring authentication.

MitigationUpdate the Order Delivery Date for WooCommerce plugin to the latest patched version immediately. If no patch is available, consider removing the plugin or implementing temporary web application firewall (WAF) rules to block SQL injection attempts.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/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. Identify plugin version
    In WordPress admin, navigate to Plugins > Installed Plugins and locate Order Delivery Date for WooCommerce to read the version number, or open the main plugin PHP file and inspect the Version header in the plugin comment block
    Affected if Version shown is 4.5.1 or below
  2. Verify plugin is enabled
    Check that the Order Delivery Date for WooCommerce plugin is activated in your WordPress installation and not simply installed but disabled
    Affected if Plugin is active and running on the site
  3. Review access logs for SQL injection patterns
    Examine web server access logs (Apache, Nginx) for incoming requests to order-delivery-date plugin endpoints containing suspicious SQL syntax such as UNION SELECT, OR 1=1, DROP TABLE, or other database commands
    Affected if Unusual SQL patterns detected in requests to the plugin

Your environment is affected if the Order Delivery Date for WooCommerce plugin version is 4.5.1 or lower and the plugin is currently active on your WordPress site.

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 the Order Delivery Date for WooCommerce plugin to the latest patched version immediately. If no patch is available, consider removing the plugin or implementing temporary web application firewall (WAF) rules to block SQL injection attempts.

Recommended fix Moderate confidence

Version 4.5.2 or later (latest available version)

  1. Navigate to WordPress admin > Plugins > Installed Plugins
  2. Locate 'Order Delivery Date for WooCommerce' in the plugin list
  3. Check the current version number to confirm it is 4.5.1 or lower
  4. Click 'Update now' if an update is available, or manually download the latest version from the WordPress plugin repository
  5. After updating, verify the new version number is higher than 4.5.1

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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