# CVE-2026-116059: LetsRecover <= 1.2.0 - Unauthenticated SQL Injection

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

The LetsRecover  WordPress plugin through 1.2.0 does not sanitize a user-supplied value that is used as a database column name in one of its unauthenticated AJAX actions, allowing unauthenticated attackers to append SQL to the query and read arbitrary data from the database, which is then returned through a second unauthenticated action.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Unknown / LetsRecover: ≥ 0; ≤ 1.2.0 (affected, semver). Source: CNA: WPScan

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-89

## Exploit evidence

- exploit: https://wpscan.com/vulnerability/4a15043f-99f3-4ba5-aecf-c9eec77220a3/ (CNA: WPScan)

## References

- https://wpscan.com/vulnerability/4a15043f-99f3-4ba5-aecf-c9eec77220a3/ (CNA: WPScan; exploit, vdb-entry, technical-description)

## Provenance

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

Revision: bcca5fec7f814bd7d9543ac866ab83dbf2ea100d7984b43b0bed823b6abcdcb7

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

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