dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-54119

CRITICAL · 10.0 CVSS v3.1 Published 2025-08-05
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
ADOdb is a PHP database class library that provides abstractions for performing queries and managing databases. In versions 5.22.9 and below, improper escaping of a query parameter may allow an attacker to execute arbitrary SQL statements when the code using ADOdb connects to a sqlite3 database and calls the metaColumns(), metaForeignKeys() or metaIndexes() methods with a crafted table name. This is fixed in version 5.22.10. To workaround this issue, only pass controlled data to metaColumns(), metaForeignKeys() and metaIndexes() method's $table parameter.

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

ADOdb versions 5.22.9 and below contain an SQL injection vulnerability in the sqlite3 driver. The metaColumns(), metaForeignKeys(), and metaIndexes() methods improperly escape the $table parameter, allowing attackers to inject arbitrary SQL statements by providing a crafted table name when connected to a sqlite3 database.

MitigationUpgrade ADOdb to version 5.22.10 or later. As a workaround, ensure only trusted/controlled data is passed to the $table parameter of these methods, and audit code using sqlite3 connections.

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
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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. Check ADOdb library version
    Locate the main ADOdb library file (typically adodb.inc.php or adodb/adodb.inc.php in the PHP include path) and look for the version definition, commonly found as define('ADODB_VERSION', '...') or in a version.php file.
    Affected if The version is 5.22.9 or below
  2. Identify sqlite3 database connections
    Search PHP codebase for connection initialization using NewADOConnection('sqlite3') or ADONewConnection('sqlite3'), or look for DSN strings containing 'sqlite3'.
    Affected if sqlite3 connections are established in the application
  3. Find usage of vulnerable methods with sqlite3
    Search for calls to $db->metaColumns(), $db->metaForeignKeys(), or $db->metaIndexes() in the code, particularly where the $table argument could come from user request parameters, API input, or external data sources.
    Affected if These methods are called with table names derived from untrusted input while using a sqlite3 connection
  4. Audit code paths passing table names to sqlite3
    Trace all code paths where table names are passed to metaColumns(), metaForeignKeys(), or metaIndexes() methods on sqlite3 connections. Check if those table names are sanitized or come from trusted sources.
    Affected if Table names passed to these methods are not hardcoded or originate from user-controlled sources

You are affected if ADOdb version is 5.22.9 or below AND you use sqlite3 database connections where the $table parameter in metaColumns(), metaForeignKeys(), or metaIndexes() can be controlled by external input.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade ADOdb to version 5.22.10 or later. As a workaround, ensure only trusted/controlled data is passed to the $table parameter of these methods, and audit code using sqlite3 connections.

Recommended fix High confidence

ADOdb version 5.22.10

  1. Identify all applications and servers using ADOdb library version 5.22.9 or below
  2. Update ADOdb to version 5.22.10 or later using your package manager (e.g., composer update adodb/adodb-php)
  3. If using a system package manager (e.g., Debian apt), update the adodb package to the latest available version
  4. Test the update in a non-production environment to verify compatibility
  5. Deploy the updated version to production servers
  6. As an additional precaution, ensure that table name parameters passed to metaColumns(), metaForeignKeys(), and metaIndexes() methods are strictly validated and only accept controlled/whitelisted input

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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