How severe is GHSA-h63c-xvpf-264j?

No CVSS score has been assigned to GHSA-h63c-xvpf-264j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h63c-xvpf-264j?

GHSA-h63c-xvpf-264j affects the following packages: adodb/adodb-php (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-h63c-xvpf-264j?

Update adodb/adodb-php to 5.20.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h63c-xvpf-264j is resolved across your whole dependency graph.

How do I detect GHSA-h63c-xvpf-264j 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-h63c-xvpf-264j 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-h63c-xvpf-264j actively exploited in the wild?

No public exploit code has been indexed for GHSA-h63c-xvpf-264j 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.

When was GHSA-h63c-xvpf-264j published, and has it been updated?

GHSA-h63c-xvpf-264j was published on May 15, 2024 and was last updated on November 29, 2024. 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

ADOdb SQL injection vulnerabilityGHSA-h63c-xvpf-264j

Fix: ADOdb/ADOdb#311

GHSA-h63c-xvpf-264j is a security vulnerability in adodb/adodb-php. A fix is available for adodb/adodb-php — see the affected versions and patch details below.

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

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

The ADOdb Library for PHP prior to version 5.20.11 is prone to SQL Injection vulnerability in multiple drivers.

Affected Packages

1 total 1 fixed

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

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.20.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h63c-xvpf-264j 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

The ADOdb Library for PHP prior to version 5.20.11 is prone to SQL Injection vulnerability in multiple drivers.

O3 Security · Impact-Aware SCA

Is GHSA-h63c-xvpf-264j in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works