CVE-2026-116059VulnerabilityPublished 13 Nov 2026

The LetsRecover WordPress plugin through 1.2.0 does not sanitize a user-supplied value that is used as a database

Source GCVE Database

Compare

Authoritative record:CVE-2026-116059· High

Not known to be exploited.

Data as of 13 Nov 2026, 07:55 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-4w56-74rv-wjqf

What to do

Affected software

Product	Affected	Fixed in
LetsRecover	Affected <=1.2.0	Fixed in–

AI-suggested

Until a fix is available, restrict access to the affected AJAX actions if possible or disable the plugin to prevent exploitation.

Description

The LetsRecover WordPress plugin up to version 1.2.0 contains a vulnerability where it does not sanitize a user-supplied value used as a database column name in an unauthenticated AJAX action. This flaw allows unauthenticated attackers to append SQL to the query and read arbitrary data from the database, which is then exposed through another unauthenticated action.

References

Community reviews

Loading reviews…