# GHSA-h63c-xvpf-264j: ADOdb SQL injection vulnerability

> An SQL injection vulnerability in the ADOdb PHP library allows attackers to manipulate database queries, potentially leading to unauthorized data access or modification.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 15 May 2024

## What is GHSA-h63c-xvpf-264j?

GHSA-h63c-xvpf-264j is a SQL injection vulnerability in adodb/adodb-php, published on 15 May 2024. It can be exploited over the network.

### Official description

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

## Which versions are affected by GHSA-h63c-xvpf-264j?

2 open source packages ship an affected version, including adodb/adodb-php.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `adodb/adodb-php` | Packagist | All versions | 5.20.11 |
| `adodb/adodb-php` | Packagist | All versions | 5.20.11 |

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

Upgrade adodb/adodb-php to 5.20.11 or later.

## Is GHSA-h63c-xvpf-264j being exploited?

There is no known exploitation of GHSA-h63c-xvpf-264j in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-h63c-xvpf-264j and fix it if it is affected.

What it is: GHSA-h63c-xvpf-264j is a SQL injection vulnerability in adodb/adodb-php, published on 15 May 2024. It can be exploited over the network.
Exploitation: There is no known exploitation of GHSA-h63c-xvpf-264j in the wild and no public exploit code.

Affected packages and fixed versions:
- adodb/adodb-php (Packagist): affected all versions; fixed in 5.20.11
- adodb/adodb-php (Packagist): affected all versions; fixed in 5.20.11

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-h63c-xvpf-264j/ (Markdown: https://insights.sbomify.com/GHSA-h63c-xvpf-264j/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-h63c-xvpf-264j

---
From sbomify Insights: https://insights.sbomify.com/GHSA-h63c-xvpf-264j/
Summaries are generated and may contain mistakes; the official description above is the record.