# GHSA-vjrg-wpm8-rhrw: doctrine/orm Regression in Query Parenthesis can have Security Implications

> Improper handling of case-insensitive checks in WHERE clauses may allow SQL injection, potentially exposing or modifying database data.

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

## What is GHSA-vjrg-wpm8-rhrw?

GHSA-vjrg-wpm8-rhrw is a SQL injection vulnerability in doctrine/orm, published on 15 May 2024. 

### Official description

An issue identified in doctrine/orm project related to statement in Where-Clause were not wrapped in brackets due to improper hadandling of case insensitive check.

## Which versions are affected by GHSA-vjrg-wpm8-rhrw?

2 open source packages ship an affected version, including doctrine/orm.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `doctrine/orm` | Packagist | From 2.8.3 | 2.8.4 |
| `doctrine/orm` | Packagist | From 2.8.3 | 2.8.4 |

## How do I fix GHSA-vjrg-wpm8-rhrw?

Upgrade doctrine/orm to 2.8.4 or later.

## Is GHSA-vjrg-wpm8-rhrw being exploited?

There is no known exploitation of GHSA-vjrg-wpm8-rhrw in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-vjrg-wpm8-rhrw and fix it if it is affected.

What it is: GHSA-vjrg-wpm8-rhrw is a SQL injection vulnerability in doctrine/orm, published on 15 May 2024. 
Exploitation: There is no known exploitation of GHSA-vjrg-wpm8-rhrw in the wild and no public exploit code.

Affected packages and fixed versions:
- doctrine/orm (Packagist): affected from 2.8.3; fixed in 2.8.4
- doctrine/orm (Packagist): affected from 2.8.3; fixed in 2.8.4

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-vjrg-wpm8-rhrw/ (Markdown: https://insights.sbomify.com/GHSA-vjrg-wpm8-rhrw/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-vjrg-wpm8-rhrw

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