CVE-2022-40218 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.1.4. Update to 1.1.5 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.1.4. Patchstack gives the patched version as 1.1.5. 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).
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.1.4 or lower is affected. Version 1.1.5 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.1.5 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
Missing authorization means a handler does its job without asking whether the caller is allowed to ask. In this plugin that applies to an unauthenticated request. Patchstack groups it with broken authentication, which fits.
The record gives no detail on the exposed function, and neither does the Patchstack summary I could read, so this post stays at the level of the advisories. The numbers show a low integrity and low availability impact with no data disclosure.
The interesting part is the version history. This CVE stops at 1.1.4, but a second CVE, CVE-2022-38057, covers the same plugin up to 1.2.1. A team that patched to 1.1.5 for this one was still exposed to the later one. Always upgrade to the newest release, not the minimum version named for a single CVE. The record's KEV flag is false, and nothing I fetched reports exploitation in the wild.
Quick check
Is 1.1.5 enough?
It fixes this CVE. A separate CVE, CVE-2022-38057, affects versions up to 1.2.1 and is fixed in 1.2.2, so aim for 1.2.2 or later.
Why are there two CVEs for one plugin?
Different flaws were found and fixed in different releases. Each gets its own identifier and its own affected range.
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.