CVE-2022-4357: The LetsRecover WordPress plugin before 1.2.0 does not properly sanitise and escape a parameter before using i

Q: How do I fix CVE-2022-4357?

letsrecover: upgrade to newer than 1.1.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-4357 being exploited?

CVE-2022-4357 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-4357 affect?

CVE-2022-4357 affects letsrecover. Severity is critical (CVSS 9.8). 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 AJAX action available to unauthenticated users, leading to a SQL injection.

Q: How urgent is CVE-2022-4357?

Priority 55/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADE

CVE-2022-4357 is a critical-severity flaw (CVSS 9.8) affecting letsrecover. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 AJAX action available to unauthenticated users, leading to a SQL injection.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.0% (top 36%)
CISA exploited list	No
Published	2023-01-02
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: letsrecover project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-01-02 22:15 UTCPublished CVE record published
2026-06-17 05:20 UTCUpdated Record last modified

letsrecover project letsrecover UPGRADE

Affected: <= 1.1.0

Fixed in: newer than 1.1.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy letsrecover || rpm -q letsrecover || letsrecover --version

2. UPGRADE to newer than 1.1.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade letsrecover

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade letsrecover

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-4357?

letsrecover: upgrade to newer than 1.1.0. Exact commands for each OS are on this page.

Is CVE-2022-4357 being exploited?

CVE-2022-4357 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-4357 affect?

CVE-2022-4357 affects letsrecover. Severity is critical (CVSS 9.8). 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 AJAX action available to unauthenticated users, leading to a SQL injection.

How urgent is CVE-2022-4357?

Priority 55/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2022-4356 HIGH 7.2 UPGRADE The LetsRecover WordPress plugin before 1.2.0 does not properly sanitise and escape a parameter before using i
CVE-2022-4355 HIGH 7.2 UPGRADE The LetsRecover WordPress plugin before 1.2.0 does not properly sanitise and escape a parameter before using i

References

← Back to latest CVEs