CVE-2026-96331
validatedZero produced an exploit or a check.GHSA-x2jq-5mqf-7hv6 ↗EUVD-2026-95610 ↗
description
Ajax Search Pro through version 4.29.1 is affected by a blind SQL injection flaw. An attacker may be able to influence database queries and infer information from their results; the advisory does not state authentication or request-path requirements.
mitigation
Treat installations through 4.29.1 as exposed and limit untrusted access to Ajax Search Pro search functionality where possible. Monitor the vendor for a confirmed corrected release and upgrade to it after validation.
outcome
Contextual check: a technique exists and was validated, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-03 00:00Z
- 2026-10-09 10:00Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-96331
{ "etk_id": "ETK-2026-1070", "cve_id": "CVE-2026-96331", "display_id": "CVE-2026-96331", "ghsa_id": "GHSA-x2jq-5mqf-7hv6", "euvd_id": "EUVD-2026-95610", "status": "published", "anchor_state": "anchored", "title": "Blind SQL injection in Ajax Search Pro", "summary": "Ajax Search Pro through version 4.29.1 is affected by a blind SQL injection flaw. An attacker may be able to influence database queries and infer information from their results; the advisory does not state authentication or request-path requirements.", "mitigation": "Treat installations through 4.29.1 as exposed and limit untrusted access to Ajax Search Pro search functionality where possible. Monitor the vendor for a confirmed corrected release and upgrade to it after validation.", "vendor": "wpdreams", "product": "Ajax Search Pro", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0, <= 4.29.1" ], "ecosystem": null, "fixed_versions": [], "package_name": "ajax-search-pro", "purl": null } ], "cwes": [ 89 ], "cvss_score": 9.3, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L", "epss_score": 0.0024, "epss_percentile": 0.1449, "epss_asof": "2026-10-20", "automation": "contextual", "check": true, "check_confidence_basis": "assessed", "exploit": false, "pipeline_minutes": 29.518892133333335, "t0_at": "2026-10-09T10:00:21.324000+00:00", "signals": { "check": { "at": "2026-10-09T11:57:17.908656+00:00", "days": 0.08121047055555555, "is_lower_bound": false, "measured_at": "2026-10-09T10:00:21.324000+00:00", "url": null }, "kev": { "at": "2026-10-03T00:00:00+00:00", "days": -6, "is_lower_bound": false, "measured_at": "2026-10-09T10:00:21.324000+00:00", "precision": "day", "url": "https://vulncheck.com/cve/CVE-2026-96331" }, "trigger_signal": { "at": "2026-10-09T10:00:21.324000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-09T10:00:21.324000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-96331" } } }
published 2026-10-09 11:31Z
last change 2026-10-21 05:31Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.