# CVE-2026-42386: WordPress Order Delivery Date for WooCommerce plugin <= 4.5.1 - SQL Injection vulnerability

> Unauthenticated attackers can execute arbitrary SQL commands via the Order Delivery Date for WooCommerce plugin, potentially accessing or modifying database contents.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-6xg5-89c9-843g

## What is CVE-2026-42386?

CVE-2026-42386 is a critical SQL injection vulnerability in tychesoftwares Order Delivery Date for WooCommerce, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unauthenticated SQL Injection in Order Delivery Date for WooCommerce <= 4.5.1 versions.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-42386?


## How do I fix CVE-2026-42386?

No fix has been published for CVE-2026-42386 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-42386 being exploited?

There is no known exploitation of CVE-2026-42386 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42386 and fix it if it is affected.

What it is: CVE-2026-42386 is a critical SQL injection vulnerability in tychesoftwares Order Delivery Date for WooCommerce, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42386 in the wild and no public exploit code.

Affected product: tychesoftwares Order Delivery Date for WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-42386/ (Markdown: https://insights.sbomify.com/CVE-2026-42386/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42386
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42386
- OSV: https://osv.dev/vulnerability/CVE-2026-42386

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-42386/
Summaries are generated and may contain mistakes; the official description above is the record.