CVE-2025-46337: SQL injection in ADOdb PostgreSQL driver pg_insert_id() method

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 0.7%, percentile 54: FIRST’s model estimates a 0.7% chance of exploitation activity in the next 30 days, higher than 54% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes adodb/adodb-php (Composer (PHP)) <= 5.22.8, fixed in 5.22.9. Check your lockfile, including transitive dependencies.

What it is

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 pginsertid() with user-supplied data. This issue has been patched in version 5.22.9.

From the GitHub advisory

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 pginsertid() with user-supplied data.

Note that the indicated Severity corresponds to a worst-case usage scenario.

Impact PostgreSQL drivers (postgres64, postgres7, postgres8, postgres9).

Patches Vulnerability is fixed in ADOdb 5.22.9 (11107d6d6e5160b62e05dff8a3a2678cf0e3a426).

Workarounds Only pass controlled data to pginsertid() method's $fieldname parameter, or escape it with pgescapeidentifier() first.

Weakness type: CWE-89.

Product: adodb/adodb-php (Composer (PHP)) · Assigned by: GitHub_M · Published: 2025-05-01

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: none (no login)
• User interaction: none
• Scope: changed (can affect other components)

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 0.74% probability of exploitation activity in the next 30 days; percentile 54.

Timeline

• 2025-05-01 — CVE record published by GitHub_M
• 2025-05-01 — GitHub-reviewed advisory GHSA-8x27-jwjr-8545 published (critical)
• 2025-05-26 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-8x27-jwjr-8545 github.com
2. CVE.org record CVE-2025-46337 cve.org
3. NVD entry CVE-2025-46337 nvd.nist.gov

Other references from the CVE record and advisory

1. github.com github.com
2. github.com github.com
3. github.com github.com
4. xaliom.blogspot.com xaliom.blogspot.com
5. lists.debian.org lists.debian.org

Critical Composer (PHP) advisories · Today’s Security Digest