dbcve.org
InjectionWeakness · CWE-74

CVE-2025-1116

HIGH · 7.3 CVSS v3.1 Published 2025-02-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability, which was classified as critical, has been found in Dreamvention Live AJAX Search Free up to 1.0.6 on OpenCart. Affected by this issue is the function searchresults/search of the file /?route=extension/live_search/module/live_search.searchresults. The manipulation of the argument keyword leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

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 · high confidence

SQL injection vulnerability in the Live AJAX Search Free extension for OpenCart. The searchresults/search function in the live_search module fails to properly sanitize the 'keyword' parameter before using it in SQL queries, allowing remote attackers to inject arbitrary SQL commands.

MitigationImplement parameterized queries (prepared statements) for all database operations involving user input, or upgrade to a patched version of the extension if available from the vendor.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Live AJAX Search Free extension is installed
    Access your OpenCart admin panel and navigate to Extensions > Extensions > Modules (or Extensions > Modules depending on version). Look for 'Live AJAX Search' or 'Live Search' in the installed modules list.
    Affected if The extension does not appear in the installed modules list.
  2. Identify the installed extension version
    In the OpenCart admin panel, click the Edit button for the Live AJAX Search module. Look for a version number displayed in the module configuration page, or check the extension's main PHP file (typically in admin/controller/module/live_search.php or catalog/controller/module/live_search.php) for a version constant or comment.
    Affected if You cannot locate a version number or the version is earlier than any patched release.
  3. Examine the search function code for the vulnerability
    On the server, locate the live_search controller file (usually in catalog/controller/module/live_search.php or catalog/controller/product/live_search.php). Open the file and locate the searchresults or search function. Inspect how the 'keyword' parameter from the request is handled before being used in SQL queries.
    Affected if The code directly incorporates the 'keyword' parameter into SQL queries without using parameterized queries, prepared statements, or input sanitization functions.
  4. Verify the vulnerable parameter is in use
    Check if the searchresults/search function accepts and processes a 'keyword' GET or POST parameter. Confirm this parameter flows into any database query without proper escaping or parameter binding.
    Affected if The 'keyword' parameter is accepted and used in SQL queries without prepared statement parameter binding.

If the Live AJAX Search Free extension is installed and the search function processes the 'keyword' parameter directly into SQL queries without parameterized queries, the environment is affected by this SQL injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries (prepared statements) for all database operations involving user input, or upgrade to a patched version of the extension if available from the vendor.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1116 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1116 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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