CVE-2026-42664
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnauthenticated Broken Access Control in AI Product Search for WooCommerce – Motive Commerce Search <= 1.38.2 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is an unauthenticated broken access control vulnerability in the Motive Commerce Search (AI Product Search for WooCommerce) WordPress plugin. The flaw allows unauthenticated attackers to access resources or perform actions that should be restricted, likely due to missing or insufficient authorization checks on certain AJAX endpoints or frontend functionality. With a CVSS 8.2 (HIGH), this poses significant risk as it can be exploited without any credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Motive Commerce Search plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Motive Commerce Search' or 'AI Product Search for WooCommerce'. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'motive-commerce-search' or similar.Affected if The plugin is installed and active
-
Identify the installed plugin versionIn WordPress admin > Plugins > Installed Plugins, find the Motive Commerce Search plugin and read the version number displayed beneath the plugin name. Compare this to the affected range (versions 1.38.2 and below).Affected if Installed version is 1.38.2 or lower
-
Inspect AJAX endpoint accessibilityExamine the plugin PHP files (typically in wp-content/plugins/motive-commerce-search/) for AJAX action hooks registered with add_action('wp_ajax_...') and add_action('wp_ajax_nopriv_...'). The presence of wp_ajax_nopriv_ hooks indicates endpoints accessible to unauthenticated users. Check if these endpoints perform sensitive operations without capability checks.Affected if AJAX endpoints are registered with nopriv hooks and lack proper capability checks or nonce validation
-
Test search functionality accessUse a browser or curl to send a request to the plugin's search AJAX endpoint (commonly /wp-admin/admin-ajax.php?action=motive_commerce_search or similar) without providing authentication cookies or a valid nonce token. Observe if the request succeeds and returns product data.Affected if The search endpoint responds to unauthenticated requests without returning an authorization error
You are affected if the Motive Commerce Search plugin version is 1.38.2 or lower and AJAX endpoints or search functionality are accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Motive Commerce Search plugin to a version newer than 1.38.2 as soon as a patched release is available. If no patched version exists, consider disabling the plugin or implementing a WAF rule to block suspicious access patterns.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42664 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-42664 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data