Skip to main content
VulnerabilityPublished Updated

CVE-2025-54119: ADOdb · SQL Injection

Affects ADOdbSource GCVE Database

0
Compare

Not known to be exploited · CVSS 10.0 Critical : upgrade to 5.22.10 as a priority.

Data as of 29 Oct 2026, 23:46 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.110.0
Patch
Available – fixed in 5.22.10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade ADOdb to 5.22.10.

Affected software

ProductAffectedFixed in
ADOdb ADOdbAffected
  • <5.22.10
Fixed in
  • 5.22.10

AI-suggested

Upgrade ADOdb to version 5.22.10 or later, where this vulnerability is fixed. As a temporary workaround, ensure that only controlled, validated data is passed to the metaColumns(), metaForeignKeys(), and metaIndexes() methods' $table parameter.

Description

ADOdb versions 5.22.9 and earlier contain a critical SQL injection vulnerability in the metaColumns(), metaForeignKeys(), and metaIndexes() methods when used with sqlite3 databases. Improper escaping of the table name parameter allows attackers to execute arbitrary SQL statements. This vulnerability is fixed in version 5.22.10.

References

Community reviews

Loading reviews…