CVE-2022-38057 is a medium severity (CVSS 6.5) missing authorization flaw in the Advance WordPress Search (Advance Product Search) plugin for WordPress, versions up to and including 1.2.1. Update to 1.2.2 or later. Check your installed version and apply the update through your normal change process.
What's affected
The record lists Advance WordPress Search (Advance Product Search) from ThemeHunk, from the first release through 1.2.1. Patchstack gives the patched version as 1.2.2. Patchstack gives the required privilege as none, so it is unauthenticated.
The record scores it 6.5 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L. Patchstack labels its own priority High. The weakness class is CWE-862 (Missing Authorization) and CWE-306 (Missing Authentication for Critical Function).
How to check if you're exposed
Start with an inventory. If you manage the site with WP-CLI, this lists every plugin with its version and whether an update is waiting:
wp plugin list --fields=name,status,version,update
Look for the folder th-advance-product-search. That folder name comes from the Patchstack entry for this issue, so confirm it matches what sits under wp-content on your site. Without WP-CLI, open the Plugins screen in the dashboard and read the version shown under the name. Version 1.2.1 or lower is affected. Version 1.2.2 or later is patched.
Check staging copies, old multisite subsites and inactive plugins too. A deactivated plugin is still on disk, and some of these bugs are reachable through files that load even when the plugin is switched off, so deactivation alone is not a fix. Delete what you do not use.
What to do now
- Update Advance WordPress Search (Advance Product Search) to 1.2.2 or a newer release.
- Review the site's user list and remove accounts you do not recognise.
- Turn on automatic updates for the plugin so the next fix lands without a ticket.
Why it matters
The two classes listed in the record, missing authorization and missing authentication for a critical function, say the same thing from two angles. A function in the plugin does its work for anyone who asks, with no login check and no capability check. Patchstack files it under broken authentication for the same reason.
The record does not describe which function is exposed, so I will not guess. The scoring tells you what to expect: network reachable, no privileges, low integrity and low availability impact, no confidentiality impact. That is a nuisance level of harm for a search widget, but a nuisance reachable by anyone on the internet is still worth a one line update.
This is also a good case for tracking by CVE rather than by plugin name. The same plugin has a sibling issue, CVE-2022-40218, with an older version range, and updating to 1.2.2 or later covers both. The record's KEV flag is false, and nothing I fetched reports exploitation in the wild.
Quick check
Is this the same plugin as CVE-2022-40218?
Yes. That CVE covers versions up to 1.1.4 with a fix in 1.1.5. This one covers versions up to 1.2.1 with a fix in 1.2.2. Moving to 1.2.2 or later covers both.
Does an attacker need an account?
No. Patchstack lists the required privilege as unauthenticated.
Sources
Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.
Last reviewed: 19 October 2026.