External risk intelligence

Ajax WooSearch WordPress SQL Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2025-9697

The vulnerability exists in a WordPress plugin that exposes an AJAX action to unauthenticated users. Since WordPress sites are commonly deployed as public-facing web applications, the affected functionality is reachable over the internet by design for standard users or visitors.

SQL Injection

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory addresses a critical vulnerability in the Ajax WooSearch WordPress plugin that could allow attackers to inject malicious SQL code into your database. This SQL injection flaw, accessible to unauthenticated users, poses a significant risk if the affected plugin is in use.

  • Unauthenticated users can inject database code.
  • Critical flaw affects widely used WordPress plugins.
  • Confirm relevance and assess exposure to this risk.

Attack Path

How an attacker could exploit the issue

An attacker can target an unauthenticated user by sending a specially crafted request to a WordPress site. This request exploits a weakness in the Ajax WooSearch plugin's handling of user input within an AJAX action. By manipulating a parameter, the attacker can inject malicious SQL code, potentially leading to unauthorized access and modification of sensitive data.

  • Entry Condition: Unauthenticated access to the website.
  • Trigger Point: Specially crafted AJAX request to the plugin.
  • Resulting Risk: SQL injection, data compromise.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to execute arbitrary SQL commands on the underlying database. This may impact the integrity and confidentiality of any data stored within that database, including potentially sensitive user or application information.

  • Database integrity and confidentiality.
  • Unauthenticated SQL injection via AJAX.
  • Data corruption or unauthorized access.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-World Ownership:

Given the plugin's nature and its exposure via unauthenticated AJAX actions, the platform or infrastructure team responsible for managing WordPress deployments is likely the first point of contact. Their initial practical move should be to identify all WordPress instances utilizing the Ajax WooSearch plugin, assess their internet reachability and business criticality, and then locate the specific application owner or system administrator accountable for each instance to coordinate remediation.

  • Platform and infrastructure teams own the issue.
  • Verify plugin use and external exposure.
  • Plan and coordinate risk-based remediation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Ajax WooSearch WordPress plugin?

Ajax WooSearch is a plugin designed to enhance the search functionality of WordPress websites, specifically those using WooCommerce for e-commerce. It allows site visitors to perform real-time product searches as they type. Developers integrate it into their themes to improve user experience, but because it handles database queries via AJAX, it must safely process all incoming user data.

What does CVE-2025-9697 mean for my data?

This CVE represents a SQL injection vulnerability. It occurs when software fails to properly clean or restrict user input before incorporating it into a database query. In this case, the plugin allows external input to reach the database, which could let an attacker execute unauthorized commands to view, change, or delete the information stored in your site's database.

How does an attacker trigger this vulnerability?

An attacker triggers this flaw by sending a specifically formatted AJAX request to the affected WordPress site. Because the plugin does not require users to be logged in to interact with this AJAX function, no account or special privileges are needed to initiate the attack. Normal site navigation or standard background requests do not trigger the issue; it requires a malicious, crafted request designed to manipulate the underlying database query.

Is my website at risk from this vulnerability?

Your risk depends on whether your site is internet-facing, as Halo Surface Signal notes that this vulnerability is reachable over the web by design. If you are using the vulnerable plugin on a public WordPress site, the functionality is accessible to anyone on the internet. Internal or private sites not reachable from the outside world would face a lower risk profile compared to publicly accessible e-commerce storefronts.

What should I do if I use this plugin?

Your first step is to perform an inventory of all your WordPress deployments to see if Ajax WooSearch is currently installed. Once you have identified which instances use this plugin, assess their business criticality and network exposure. Coordinate with the relevant system administrators to determine the next steps for risk management, such as disabling the plugin until an official update is available.

References