CVE-2022-4356 json
LetsRecover < 1.2.0 - Admin+ SQLi
published 3y ago modified 4mo ago also EUVD-2022-51707
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
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
Patch / fix
- Unknown LetsRecover 1.2.0
Is CVE-2022-4356 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.97% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/27a8d7cb-e179-408e-af13-8722ab41947b referenced PoC, tagged "exploit" by a source, unverified
- wpscan.com https://wpscan.com/vulnerability/27a8d7cb-e179-408e-af13-8722ab41947b/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Unknown LetsRecover
Classification
- Technology feeds
References
-
wpscan.com
/vulnerability/27a8d7cb-e179-408e-af13-8722ab41947b
exploit, vdb-entry, technical-description, third-party-advisory
-
wpscan.com
/vulnerability/27a8d7cb-e179-408e-af13-8722ab41947b/
exploit
-
bulletin.iese.de
/post/letsrecover-woocommerce-abandoned-cart_1-1-0_3
broken-link, third-party-advisory
Sources
- CVE List CVE-2022-4356
- NVD CVE-2022-4356
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.