How severe is CVE-2022-4356?

CVE-2022-4356 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2022-4356 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (55th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2022-4356?

CVE-2022-4356 affects Letsrecover Project Letsrecover. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2022-4356?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2022-4356 published?

CVE-2022-4356 was published on 2023-01-02 and last updated on 2026-06-17.

CVE-2022-4356

CVE-2022-4356 is a high-severity vulnerability in Letsrecover Project Letsrecover with a CVSS 3.x base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.2)
EPSS exploit prediction: 1% (55th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Letsrecover Project Letsrecover
Published: 2023-01-02
Last modified: 2026-06-17

Description

The LetsRecover WordPress plugin before 1.2.0 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by high privilege users such as admin

Frequently asked questions

What is 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 to a SQL injection exploitable by high privilege users such as admin
How severe is CVE-2022-4356?: CVE-2022-4356 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2022-4356 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (55th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-4356?: CVE-2022-4356 affects Letsrecover Project Letsrecover. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-4356?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2022-4356 published?: CVE-2022-4356 was published on 2023-01-02 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:letsrecover_project:letsrecover:*:*:*:*:*:wordpress:*:*

More vulnerabilities in Letsrecover Project Letsrecover

CVE-2022-4357 — 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…
CVE-2022-4355 — High (CVSS 7.2): The LetsRecover WordPress plugin before 1.2.0 does not properly sanitise and escape a parameter before using it in a…

All CVEs affecting Letsrecover Project Letsrecover →