dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-67921

HIGH · 8.5 CVSS v3.1 Published 2026-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in VanKarWai Lobo lobo allows Blind SQL Injection.This issue affects Lobo: from n/a through < 2.8.6.

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

VanKarWai Lobo lobo before version 2.8.6 contains a blind SQL injection vulnerability. An attacker can inject malicious SQL queries through unsanitized input parameters, potentially allowing extraction of sensitive data from the database or manipulation of database contents. Blind SQL injection means the application does not directly display SQL errors but the attacker can infer information based on application behavior differences.

MitigationUpgrade VanKarWai Lobo to version 2.8.6 or later. Until a patch is available, implement input validation and convert all SQL queries to use parameterized queries or prepared statements to prevent SQL injection.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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. Identify if Lobo web application is present
    Search for Lobo installation directories or check running web services for Lobo (look for 'lobo' in process names, service definitions, or web server configurations)
    Affected if Lobo web application is found running in the environment
  2. Determine installed Lobo version
    Locate version information in Lobo installation: check version file, about page, or metadata files within the Lobo directory structure
    Affected if Version is found to be 2.8.5 or earlier, or version cannot be determined (unknown versions should be treated as vulnerable)
  3. Identify user input points that interact with databases
    Review application source code or configuration to find where user-supplied parameters (GET/POST requests, headers, cookies) are used in SQL query construction without visible parameterization
    Affected if User input fields are used directly in SQL queries without evident prepared statements or input sanitization
  4. Test input fields for blind SQL injection behavior
    Submit SQL-specific payloads (such as time-delay commands like SLEEP() or conditional responses) to application input fields and observe application response times or behavior differences
    Affected if Application exhibits delayed responses or different behavior based on injected SQL syntax, indicating the input is not properly sanitized before being used in queries

Environment is affected if Lobo web application is present and the installed version is 2.8.5 or earlier, or if user input fields process SQL syntax without sanitization.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade VanKarWai Lobo to version 2.8.6 or later. Until a patch is available, implement input validation and convert all SQL queries to use parameterized queries or prepared statements to prevent SQL injection.

Recommended fix High confidence

2.8.6

  1. Backup your current Lobo installation and database before upgrading
  2. Download Lobo version 2.8.6 from the official VanKarWai source
  3. Replace the existing Lobo files with the new version 2.8.6 files
  4. Verify the installation and test that the application functions correctly
  5. Confirm the SQL injection vulnerability is no longer present

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67921 — 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-67921 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