# CVE-2026-39542: WordPress Doofinder for WooCommerce plugin <= 2.10.13 - Sensitive Data Exposure vulnerability

> An attacker can retrieve sensitive data exposed by the Doofinder for WooCommerce plugin, potentially compromising user or store information.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-vv3p-7ggx-8fch

## What is CVE-2026-39542?

CVE-2026-39542 is a medium-severity vulnerability in Doofinder for WooCommerce, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insertion of Sensitive Information Into Sent Data vulnerability in Doofinder Doofinder for WooCommerce doofinder-for-woocommerce allows Retrieve Embedded Sensitive Data.This issue affects Doofinder for WooCommerce: from n/a through <= 2.10.13.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

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


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

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

## Is CVE-2026-39542 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-39542 is a medium-severity vulnerability in Doofinder for WooCommerce, published on 8 Apr 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-39542 in the wild and no public exploit code.

Affected product: Doofinder 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-39542/ (Markdown: https://insights.sbomify.com/CVE-2026-39542/index.md)
```

## Sources

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

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