How severe is GHSA-vjrg-wpm8-rhrw?

No CVSS score has been assigned to GHSA-vjrg-wpm8-rhrw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vjrg-wpm8-rhrw?

GHSA-vjrg-wpm8-rhrw affects the following packages: doctrine/orm (Packagist). Ecosystems affected: Packagist.

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

Update doctrine/orm to 2.8.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vjrg-wpm8-rhrw is resolved across your whole dependency graph.

How do I detect GHSA-vjrg-wpm8-rhrw in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for doctrine/orm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-vjrg-wpm8-rhrw if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-vjrg-wpm8-rhrw actively exploited in the wild?

No public exploit code has been indexed for GHSA-vjrg-wpm8-rhrw 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-vjrg-wpm8-rhrw published, and has it been updated?

GHSA-vjrg-wpm8-rhrw 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

doctrine/orm Regression in Query Parenthesis can have Security ImplicationsGHSA-vjrg-wpm8-rhrw

Fix: doctrine/orm#8591

GHSA-vjrg-wpm8-rhrw is a security vulnerability in doctrine/orm. A fix is available for doctrine/orm — 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

🐘doctrine/orm

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

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`doctrine/orm`	≥ 2.8.3&&< 2.8.4	2.8.4`composer require doctrine/orm:^2.8.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for doctrine/orm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update doctrine/orm to 2.8.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vjrg-wpm8-rhrw is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-vjrg-wpm8-rhrw in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works