Skip to main content

Ajax Search Lite CVE-2026-111852

| EUVDEUVD-2026-107273 CRITICAL
SQL Injection (CWE-89)
2026-10-21 Patchstack GHSA-rxg4-hh2m-h7g8
9.3
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify site running Ajax Search Lite
  2. Delivery
    Send crafted search request with SQL payload
  3. Exploit
    Trigger blind SQL injection in query
  4. Execution
    Infer database contents via boolean/time responses
  5. Impact
    Exfiltrate sensitive data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires only that the WPdreams Ajax Search Lite plugin (version n/a through 4.14.6) be installed and active on an internet-reachable WordPress site; the search endpoint is exposed to anonymous visitors by design, so no authentication, no special configuration, and no user interaction are needed (AV:N/AC:L/PR:N/UI:N). The primary limiting factor is deployment: only sites running this specific plugin at or below 4.14.6 are affected. The 'Blind' nature limits data retrieval speed (inference-based rather than direct output), making exploitation noisier and more time-consuming but still fully automatable.

Impact

This is a genuinely high-priority vulnerability by its technical profile. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes a remotely exploitable, low-complexity, unauthenticated blind SQL injection - the most dangerous combination of access conditions, requiring no credentials or user interaction. The scope-change flag (S:C) and C:H drive the 9.3 score, reflecting that a compromised database can expose data beyond the immediate component. However, several real-world risk signals are MISSING from the input: there is NO EPSS probability score provided, NO CISA KEV listing, and NO indication of public exploit code. Per precision rules, exploitation status is 'no public exploit identified at time of analysis.' The I:N/A:L split and the 'Blind' qualifier are consistent - blind SQLi is primarily a confidentiality/data-exfiltration issue extracted inference-by-inference, which is slower and more detectable than error-based SQLi but fully automatable with standard tooling (e.g. sqlmap). Net assessment: a real priority for any site running this plugin due to unauthenticated network reach and the well-known ease of automating WordPress plugin SQLi, but the absence of EPSS/KEV/POC data means active-exploitation risk cannot be confirmed from the provided sources and should be verified against Patchstack and public exploit feeds.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends crafted requests to a public-facing WordPress site running Ajax Search Lite (<= 4.14.6), injecting SQL through a vulnerable search parameter. Because the flaw is blind, the attacker uses boolean- or time-based inference (easily automated with tools like sqlmap) to extract sensitive database contents such as user records and password hashes. No public exploit code is identified in the provided data, but the AV:N/AC:L/PR:N/UI:N profile makes exploitation straightforward if a working payload is developed.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

Blind SQL injection in WPdreams Ajax Search Lite through version 4.14.6 allows unauthenticated remote attackers to extract sensitive data from the WordPress database by inferring query results. The plugin's public-facing search endpoint is exposed to anonymous visitors by design, so no authentication or user interaction is required. No public exploit code was identified at the time of analysis, but the vulnerability is fully automatable and high severity.

RemediationAI

No vendor-released patch was identified at the time of analysis; consult the Patchstack advisory for a fixed version and upgrade beyond 4.14.6 as soon as one is confirmed. Until then, disable the Ajax Search Lite plugin-this removes the vulnerable public search endpoint but also eliminates site search functionality. As compensating controls, deploy WAF rules that detect SQL injection patterns on the plugin's AJAX endpoint, accepting possible false positives and evasion risk; enable virtual patching through a WordPress security plugin; and monitor database and web logs for anomalous AJAX search requests, though this is detective only. Restricting access to the endpoint is impractical because it is designed for anonymous visitors.

Affected VersionsENISA

Ajax Search Lite 0 ≤4.14.6

Affected Packages

euvd ajax_search_lite no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is a CWE-89 SQL injection in the WPdreams Ajax Search Lite plugin for WordPress. The plugin handles AJAX search requests and fails to properly neutralize special elements in SQL commands, allowing attacker-controlled input to alter database queries. Because the injection is blind, the attacker cannot see direct query output and must use boolean- or time-based inference to reconstruct data. The CPE cpe:2.3:a:wpdreams:ajax_search_lite:*:*:*:*:*:*:*:* confirms all versions up to and including 4.14.6 are in scope. WordPress plugins run with the privileges of the WordPress database user, so successful exploitation can expose user credentials, posts, and other stored data.

Know when Ajax Search Lite gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 9.3 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
vuln.today AI 8.2 HIGH

Unauthenticated network-reachable search endpoint gives AV:N/AC:L/PR:N/UI:N; blind SQLi primarily exfiltrates data (C:H) with limited write potential (I:L), scope unchanged within the DB (S:U).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

DescriptionCVE.org

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in WPdreams Ajax Search Lite ajax-search-lite allows Blind SQL Injection.This issue affects Ajax Search Lite: from n/a through 4.14.6.

Executive ViewAI

Why It Matters

WPdreams Ajax Search Lite, a WordPress plugin affecting versions through 4.14.6, contains a critical blind SQL injection vulnerability that could allow extraction of sensitive data from the underlying database. No public exploit identified at time of analysis, but the flaw is fully automatable and could expose user credentials, customer information, and proprietary content, creating data breach, regulatory, and reputational risk. With no vendor-released patch identified at time of analysis, leadership should ensure compensating controls are deployed immediately.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: disable or remove WPdreams Ajax Search Lite (through version 4.14.6) if not essential; deploy WAF rules to detect and block SQL injection attempts against the plugin's search endpoint; restrict public access to the endpoint where operationally feasible; monitor web and database logs for anomalous query patterns; enforce least-privilege database accounts; and apply virtual patching until a vendor fix is released.

Threat Intelligence Overview

EPSS Score
0.3%
Top 74% exploitable
Prevalence
Medium
popular WordPress search plugin, common but not universally deployed
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy