Predictive Search <= 1.2.2 - Missing Authorization
Strategic Overview
- Status
- Patched in 1.2.3
- Affected Plugin
- Predictive Search
- Affected Version
<= 1.2.2- CVSS
- 6.5Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE pending
At a glance
This record tracks a medium-severity Missing Authorization vulnerability in the Predictive Search WordPress plugin, affecting versions <= 1.2.2. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.3; sites on affected versions should update now. Disclosed May 2023.
Vulnerability Overview
The Predictive Search plugin for WordPress is vulnerable to unauthorized modification and disclosure of data due to missing capability checks on the wp_predictive_search_start_sync_ajax, wp_predictive_search_sync_taxonomy_ajax, wp_predictive_search_sync_relationships_ajax, wp_predictive_search_sync_posts_ajax, wp_predictive_search_manual_sync_error_ajax, and wp_predictive_search_sync_end_ajax functions called via wp_ajax and wp_ajax_nopriv hooks in versions up to, and including, 1.2.2. This makes it possible for unauthenticated attackers to conduct search syncs and read and data returned in the response.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in Predictive Search <= 1.2.2 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Predictive Search the fix is 1.2.3: builds <= 1.2.2 are affected, anything from 1.2.3 onward is not.
Remediation
Update to version 1.2.3, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Predictive Search 1.2.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C