# GHSA-27qr-636m-wxg2: codeigniter/framework SQL injection in ODBC database driver


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 15 May 2024

## What is GHSA-27qr-636m-wxg2?

GHSA-27qr-636m-wxg2 is a vulnerability in codeigniter/framework, published on 15 May 2024. 

### Official description

CodeIgniter 3.1.0 addressed a critical security issue within the ODBC database driver. This update includes crucial fixes to mitigate a SQL injection vulnerability, preventing potential exploitation by attackers. It is noteworthy that these fixes render the query builder and escape() functions incompatible with the ODBC driver. However, the update introduces actual query binding as a more secure alternative.

## Which versions are affected by GHSA-27qr-636m-wxg2?

2 open source packages ship an affected version, including codeigniter/framework.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `codeigniter/framework` | Packagist | All versions | 3.1.0 |
| `codeigniter/framework` | Packagist | All versions | 3.1.0 |

## How do I fix GHSA-27qr-636m-wxg2?

Upgrade codeigniter/framework to 3.1.0 or later.

## Is GHSA-27qr-636m-wxg2 being exploited?

There is no known exploitation of GHSA-27qr-636m-wxg2 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-27qr-636m-wxg2 and fix it if it is affected.

What it is: GHSA-27qr-636m-wxg2 is a vulnerability in codeigniter/framework, published on 15 May 2024. 
Exploitation: There is no known exploitation of GHSA-27qr-636m-wxg2 in the wild and no public exploit code.

Affected packages and fixed versions:
- codeigniter/framework (Packagist): affected all versions; fixed in 3.1.0
- codeigniter/framework (Packagist): affected all versions; fixed in 3.1.0

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-27qr-636m-wxg2/ (Markdown: https://insights.sbomify.com/GHSA-27qr-636m-wxg2/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-27qr-636m-wxg2

---
From sbomify Insights: https://insights.sbomify.com/GHSA-27qr-636m-wxg2/
Summaries are generated and may contain mistakes; the official description above is the record.