How to verify CVE-2022-21661
Confirm whether your systems are actually affected — run the exact detection check below (Nuclei command or OpenVAS NVT). Detection only; it does not exploit.
How to verify this vulnerability
Scanner data tells you how to confirm whether your systems are actually affected — not just that the CVE exists. Run a Nuclei template against your target for a yes/no answer in seconds.
nuclei -id CVE-2022-21661 -u https://your-target -rl 50 -timeout 10Runs against your own host. Don't have Nuclei? Install guide ↗
- highOfficialVerifiedhttpWordPress <5.8.3 - SQL InjectionGitHub ↗
- highCommunityhttpWordPress Core < 5.8.3 - SQL Injection via WP_QueryGitHub ↗
- highCommunityhttpWordPress Core < 5.8.3 - SQL Injection via WP_Query GitHub ↗
Find every CVE you can verify
Search the whole database by Nuclei coverage — filter by vendor, severity and KEV to build a verification list for your entire stack.
- Filter all CVEs that ship a Nuclei template
- Combine with vendor, severity & KEV
- Build a scan list across your stack
This template is on GitHub already — an account lets you search and filter every CVE that has one, not just this CVE.
Verify with OpenVAS
Greenbone/OpenVAS ships 8 NVT checks for CVE-2022-21661. OpenVAS detects this CVE by NVT OID — enable the NVT in your scan config, or confirm it is in your feed with the query below.
gvm-cli socket --xml "<get_nvts nvt_oid='1.3.6.1.4.1.25623.1.0.147396' details='1'/>"1.3.6.1.4.1.25623.1.0.147396since 2026-06-251.3.6.1.4.1.25623.1.0.147397since 2026-06-251.3.6.1.4.1.25623.1.0.705039since 2026-06-251.3.6.1.4.1.25623.1.0.819542since 2026-06-251.3.6.1.4.1.25623.1.0.819544since 2026-06-251.3.6.1.4.1.25623.1.0.892884since 2026-06-251.3.6.1.4.1.25623.1.1.1.1.2022.5039since 2026-06-251.3.6.1.4.1.25623.1.1.1.2.2022.2884since 2026-06-25