PatchTheCVEletsrecover vulnerabilities and fixes
Recent CVEs affecting letsrecover, with upgrade or downgrade steps. 3 tracked.
letsrecover has 3 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 3. Most recent: 2023-01-02. Highest priority: CVE-2022-4357 (score 55/100).
- CVE-2022-4357 CRITICAL 9.8 UPGRADE The LetsRecover WordPress plugin before 1.2.0 does not properly sanitise and escape a parameter before using i
- 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
FAQ
How do I fix letsrecover vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is letsrecover being exploited right now?
None of the tracked letsrecover CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which letsrecover CVE should I patch first?
CVE-2022-4357 currently ranks highest (55/100): The LetsRecover WordPress plugin before 1.2.0 does not properly sanitise and escape a parameter before using i.