How severe is GHSA-8x27-jwjr-8545?

GHSA-8x27-jwjr-8545 has a CVSS score of 10/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-8x27-jwjr-8545?

GHSA-8x27-jwjr-8545 affects the following packages: adodb/adodb-php (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-8x27-jwjr-8545?

Update adodb/adodb-php to 5.22.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8x27-jwjr-8545 is resolved across your whole dependency graph.

How do I detect GHSA-8x27-jwjr-8545 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for adodb/adodb-php, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-8x27-jwjr-8545 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is GHSA-8x27-jwjr-8545 actively exploited in the wild?

No public exploit code has been indexed for GHSA-8x27-jwjr-8545 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-8x27-jwjr-8545?

GHSA-8x27-jwjr-8545 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-8x27-jwjr-8545?

GHSA-8x27-jwjr-8545 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-8x27-jwjr-8545 published, and has it been updated?

GHSA-8x27-jwjr-8545 was published on May 1, 2025 and was last updated on May 26, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

CRITICAL severity

SQL injection in ADOdb PostgreSQL driver pg_insert_id() methodGHSA-8x27-jwjr-8545

CRITICALFix: ADOdb/ADOdb@11107d6

GHSA-8x27-jwjr-8545 is a critical-severity (CVSS 10) SQL Injection vulnerability in adodb/adodb-php. A fix is available for adodb/adodb-php — see the affected versions and patch details below.

Also known asCVE-2025-46337

Published

May 1, 2025

Updated

May 26, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-8x27-jwjr-8545.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘adodb/adodb-php

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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 pg_insert_id() method's $fieldname parameter, or escape it with pg_escape_identifier() first.

References

Issue https://github.com/ADOdb/ADOdb/issues/1070
Blog post by Marco Nappi

Credits

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`adodb/adodb-php`	all versions	5.22.9`composer require adodb/adodb-php:^5.22.9`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for adodb/adodb-php, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update adodb/adodb-php to 5.22.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8x27-jwjr-8545 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

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. 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 pg_insert_id() method's $fieldname parameter, or escape it with pg_escape_identifier() first.