dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-46337

CRITICAL · 10.0 CVSS v3.1 Published 2025-05-01
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. Prior to version 5.22.9, improper escaping of a query parameter may allow an attacker to execute arbitrary SQL statements when the code using ADOdb connects to a PostgreSQL database and calls pg_insert_id() with user-supplied data. This issue has been patched in version 5.22.9.

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 ADOdb's pg_insert_id() function allows arbitrary SQL execution when connecting to PostgreSQL databases due to improper escaping of query parameters. An attacker can inject malicious SQL through user-supplied data passed to this function.

MitigationUpgrade ADOdb to version 5.22.9 or later. Conduct code review to identify and audit all pg_insert_id() calls, validating that user input is properly sanitized before reaching this function.

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. Locate ADOdb installation and determine version
    Search for adodb directories or files in your project (commonly named 'adodb', 'ADOdb', or included via package managers). Check for a version file or composer.json entry showing the adodb version.
    Affected if The installed ADOdb version is below 5.22.9 (or version cannot be determined and pg_insert_id is in use)
  2. Verify PostgreSQL database connectivity is in use
    Inspect your application's database configuration files, connection strings, or database driver settings. Look for 'pgsql', 'postgres', or 'postgresql' in connection parameters.
    Affected if Your application connects to PostgreSQL databases using ADOdb
  3. Identify pg_insert_id() function calls in codebase
    Search your codebase for occurrences of 'pg_insert_id' - this may appear as '$db->pg_insert_id()' or direct function calls within ADOdb's PostgreSQL driver files.
    Affected if The pg_insert_id() function is called within your application code or inherited from ADOdb
  4. Audit data flow to pg_insert_id() for unsanitized input
    Review all call sites of pg_insert_id() and trace whether user-supplied data (request parameters, user variables, external API inputs) reaches this function without parameterized queries or input validation.
    Affected if User-controllable data is passed directly to pg_insert_id() without sanitization or prepared statements

Your environment is affected if you use ADOdb versions below 5.22.9, connect to PostgreSQL databases, and have pg_insert_id() being called with unsanitized user input flowing into the query parameters.

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.9 or later. Conduct code review to identify and audit all pg_insert_id() calls, validating that user input is properly sanitized before reaching this function.

Recommended fix High confidence

5.22.9

  1. Locate the ADOdb library in your project (check composer.json, include files, or vendor directory)
  2. Determine the current ADOdb version in use
  3. Update ADOdb to version 5.22.9 or later. If using Composer, run: composer require adodb/adodb:v5.22.9 or composer update adodb/adodb
  4. If not using Composer, download version 5.22.9 from the official ADOdb repository (github.com/ADOdb/ADOdb) and replace the existing library files
  5. After upgrading, test all code paths that call pg_insert_id() with user-supplied data when connected to PostgreSQL databases to verify the SQL injection vulnerability is remediated
  6. Run your application's test suite to ensure no regressions were introduced by the upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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