Skip to content
Fencer Intel
critical 9.8

CVE-2022-0787 json

Limit Login Attempts (Spam Protection) < 5.1 - Unauthenticated SQLi

published 4y ago modified 4mo ago also EUVD-2022-15839

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
7.5%
EPSS 7.5% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known, plus a Nuclei check

Summary

The Limit Login Attempts (Spam Protection) WordPress plugin before 5.1 does not sanitise and escape some parameters before using them in SQL statements via AJAX actions (available to unauthenticated users), leading to SQL Injections

Patch / fix

  • limit_login_attempts_project limit_login_attempts 5.1

Is CVE-2022-0787 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 Fencer

Exploit prediction

7.52% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template Limit Login Attempts (Spam Protection) < 5.1 - SQL Injection nuclei detection template
  • wpscan.com https://wpscan.com/vulnerability/69329a8a-2cbe-4f99-a367-b152bd85b3dd referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • Unknown Limit Login Attempts (Spam Protection)

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command
Technology feeds

References

Sources

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.