Skip to content

The ADOdb sqlite3 driver allows SQL injection

Critical severity GitHub Reviewed Published Aug 3, 2025 in ADOdb/ADOdb • Updated Aug 5, 2025

Package

composer adodb/adodb-php (Composer)

Affected versions

<= 5.22.9

Patched versions

5.22.10

Description

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.

Note that the indicated Severity corresponds to a worst-case usage scenario, e.g. allowing user-supplied data to be sent as-is to the above-mentioned methods.

Impact

SQLite3 driver.

Patches

Vulnerability is fixed in ADOdb 5.22.10 (ADOdb/ADOdb@5b8bd52).

Workarounds

Only pass controlled data to metaColumns(), metaForeignKeys() and metaIndexes() method's $table parameter.

Credits

Thanks to Marco Nappi (@mrcnpp) for reporting this vulnerability.

References

@dregad dregad published to ADOdb/ADOdb Aug 3, 2025
Published to the GitHub Advisory Database Aug 4, 2025
Reviewed Aug 4, 2025
Published by the National Vulnerability Database Aug 5, 2025
Last updated Aug 5, 2025

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(12th percentile)

Weaknesses

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Learn more on MITRE.

CVE ID

CVE-2025-54119

GHSA ID

GHSA-vf2r-cxg9-p7rf

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.