# CVE-2026-122060: WP Recipe Maker < 10.9.2 - Unauthenticated Password-Protected Recipe Disclosure

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

The WP Recipe Maker WordPress plugin before 10.9.2 does not check whether the post a recipe is embedded in is password protected before returning the recipe through its REST API and structured data output, allowing unauthenticated users to read the full content of recipes in password-protected posts.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Unknown / WP Recipe Maker: ≥ 0; < 10.9.2 (affected, semver). Source: CNA: WPScan

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-200

## Exploit evidence

- exploit: https://wpscan.com/vulnerability/7436c1e7-16ce-438e-8734-dea0e6a9117a/ (CNA: WPScan)

## References

- https://wpscan.com/vulnerability/7436c1e7-16ce-438e-8734-dea0e6a9117a/ (CNA: WPScan; exploit, vdb-entry, technical-description)

## Provenance

- CNA: WPScan: https://www.cve.org/CVERecord?id=CVE-2026-122060; retrieved 2026-11-08; source updated 2026-11-08

Revision: 83cae792f163b2f9d1fb14833cfd666d86e3d5f5694d77787354cddc326fefba

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

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