# GHSA-x7p5-p2c9-phvg: Unexpected database bindings

> Attackers can manipulate query bindings by sending arrays for non-array fields, potentially causing the query builder to return unexpected results.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Feb 2021

## What is GHSA-x7p5-p2c9-phvg?

GHSA-x7p5-p2c9-phvg is a SQL injection vulnerability in illuminate/database, published on 2 Feb 2021. It can be exploited over the network, with no action from the victim.

### Official description

This is a follow-up to the previous security advisory (GHSA-3p32-j457-pg5x) which addresses a few additional edge cases.

If a request is crafted where a field that is normally a non-array value is an array, and that input is not validated or cast to its expected type before being passed to the query builder, an unexpected number of query bindings can be added to the query. In some situations, this will simply lead to no results being returned by the query builder; however, it is possible certain queries could be affected in a way that causes the query to return unexpected results.

## Which versions are affected by GHSA-x7p5-p2c9-phvg?

12 open source packages ship an affected version, including illuminate/database and laravel/framework.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `illuminate/database` | Packagist | All versions | 6.20.14 |
| `illuminate/database` | Packagist | All versions | 6.20.14 |
| `illuminate/database` | Packagist | From 7.0.0 | 7.30.4 |
| `illuminate/database` | Packagist | From 7.0.0 | 7.30.4 |
| `illuminate/database` | Packagist | From 8.0.0 | 8.24.0 |
| `illuminate/database` | Packagist | From 8.0.0 | 8.24.0 |
| `laravel/framework` | Packagist | All versions | 6.20.14 |
| `laravel/framework` | Packagist | All versions | 6.20.14 |
| `laravel/framework` | Packagist | From 7.0.0 | 7.30.4 |
| `laravel/framework` | Packagist | From 7.0.0 | 7.30.4 |
| `laravel/framework` | Packagist | From 8.0.0 | 8.24.0 |
| `laravel/framework` | Packagist | From 8.0.0 | 8.24.0 |

## How do I fix GHSA-x7p5-p2c9-phvg?

Upgrade illuminate/database to a fixed version for your release line: 6.20.14, 7.30.4 or 8.24.0.

## Is GHSA-x7p5-p2c9-phvg being exploited?

There is no known exploitation of GHSA-x7p5-p2c9-phvg in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-x7p5-p2c9-phvg and fix it if it is affected.

What it is: GHSA-x7p5-p2c9-phvg is a SQL injection vulnerability in illuminate/database, published on 2 Feb 2021. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-x7p5-p2c9-phvg in the wild and no public exploit code.

Affected packages and fixed versions:
- illuminate/database (Packagist): affected all versions; fixed in 6.20.14
- illuminate/database (Packagist): affected all versions; fixed in 6.20.14
- illuminate/database (Packagist): affected from 7.0.0; fixed in 7.30.4
- illuminate/database (Packagist): affected from 7.0.0; fixed in 7.30.4
- illuminate/database (Packagist): affected from 8.0.0; fixed in 8.24.0
- illuminate/database (Packagist): affected from 8.0.0; fixed in 8.24.0
- laravel/framework (Packagist): affected all versions; fixed in 6.20.14
- laravel/framework (Packagist): affected all versions; fixed in 6.20.14
- laravel/framework (Packagist): affected from 7.0.0; fixed in 7.30.4
- laravel/framework (Packagist): affected from 7.0.0; fixed in 7.30.4
- laravel/framework (Packagist): affected from 8.0.0; fixed in 8.24.0
- laravel/framework (Packagist): affected from 8.0.0; fixed in 8.24.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-x7p5-p2c9-phvg/ (Markdown: https://insights.sbomify.com/GHSA-x7p5-p2c9-phvg/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-x7p5-p2c9-phvg

---
From sbomify Insights: https://insights.sbomify.com/GHSA-x7p5-p2c9-phvg/
Summaries are generated and may contain mistakes; the official description above is the record.