Is letsrecover (WordPress plugin) vulnerable?

WordPress letsrecover has 3 known advisories in the phpwarden feed. Feed 2026.10.28.3, updated 2026-10-28.

3advisories

1critical

0on CISA KEV

3no fix recorded

CVE	Title	Severity	CVSS	Affected	Fixed in
CVE-2022-4357	The LetsRecover WordPress plugin before 1.2.0 does not properly sanitise and escape a parameter before using it in a SQL statement via an AJ	critical	9.8	`<=1.1.0`	–
CVE-2022-4355	The LetsRecover WordPress plugin before 1.2.0 does not properly sanitise and escape a parameter before using it in a SQL statement, leading	high	7.2	`<=1.1.0`	–
CVE-2022-4356	The LetsRecover WordPress plugin before 1.2.0 does not properly sanitise and escape a parameter before using it in a SQL statement, leading	high	7.2	`<=1.1.0`	–

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs How findings are ranked

A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.