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

Status: published. Published: 2026-11-04. Updated: 2026-11-04.

Insertion of Sensitive Information into Externally-Accessible File or Directory 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.17.2.

## Remediation

- fix: Update the WordPress Doofinder for WooCommerce plugin to the latest available version (at least 2.17.3). (source: CNA: Patchstack)

## Affected products and versions

- Doofinder / Doofinder for WooCommerce (doofinder-for-woocommerce): ≥ 0; ≤ 2.17.2 (affected, custom); unaffected at 2.17.3. Source: CNA: Patchstack

## Severity and prioritization

- CVSS 3.1: 7.5 (high); CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N; source: CNA: Patchstack

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-538

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://patchstack.com/database/wordpress/plugin/doofinder-for-woocommerce/vulnerability/wordpress-doofinder-for-woocommerce-plugin-2-17-2-sensitive-data-exposure-vulnerability?_s_id=cve (CNA: Patchstack; vdb-entry)

## Provenance

- CNA: Patchstack: https://www.cve.org/CVERecord?id=CVE-2026-56065; retrieved 2026-11-04; source updated 2026-11-04

Revision: 27200f190e95d11e10a9fe91c72532aa92fe6333b3d32f0b120f3e7cf4926aba

Canonical: https://y2.dev/cve/CVE-2026-56065

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.