CVE-2022-4297: The WP AutoComplete Search WordPress plugin through 1.0.4 does not sanitise and escape a parameter before usin
CVE-2022-4297 is a critical-severity flaw (CVSS 9.8) affecting wp autocomplete search. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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
Why this priority
- Critical severity
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 3.6% (top 10%) |
| CISA exploited list | No |
| Published | 2023-01-02 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Public exploits and detection
Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.
- Exploit-DB: WP AutoComplete 1.0.4 - Unauthenticated SQLi
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-4297?
wp autocomplete search: upgrade to newer than 1.0.4. Exact commands for each OS are on this page.
Is CVE-2022-4297 being exploited?
CVE-2022-4297 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-4297 affect?
CVE-2022-4297 affects wp autocomplete search. Severity is critical (CVSS 9.8). 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
How urgent is CVE-2022-4297?
Priority 67/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action