CVE-2022-4297 json
WP AutoComplete Search <= 1.0.4 - Unauthenticated SQLi
published 3y ago modified 4mo ago also EUVD-2022-51653
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.8%
- EPSS 3.8% chance of exploitation in 30 days, percentile 90%
- public exploits
- 1
- Exploit-DB
Summary
The WP AutoComplete Search WordPress plugin through 1.0.4 does not sanitise and escape a parameter before using it in a SQL statement via an AJAX available to unauthenticated users, leading to an unauthenticated SQL injection
Is CVE-2022-4297 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 FencerTimeline
- Published
- First public exploit (EDB-51560)
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
3.85% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-51560 WP AutoComplete 1.0.4 - Unauthenticated SQLi webapps, 2023-07-03
- wpscan.com https://wpscan.com/vulnerability/e2dcc76c-65ac-4cd6-a5c9-6d813b5ac26d referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Unknown WP AutoComplete Search
Classification
- Technology feeds
References
-
wpscan.com
/vulnerability/e2dcc76c-65ac-4cd6-a5c9-6d813b5ac26d
exploit, vdb-entry, technical-description, third-party-advisory
- packetstormsecurity.com /files/173293/WordPress-WP-AutoComplete-Search-1.0.4-SQL-Injection.html
Sources
- CVE List CVE-2022-4297
- NVD CVE-2022-4297
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.