How severe is GHSA-6q9v-4hq6-5m67?

No CVSS score has been assigned to GHSA-6q9v-4hq6-5m67 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6q9v-4hq6-5m67?

GHSA-6q9v-4hq6-5m67 affects the following packages: doctrine/orm (Packagist), doctrine/orm (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-6q9v-4hq6-5m67?

Update doctrine/orm to 2.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6q9v-4hq6-5m67 is resolved across your whole dependency graph.

How do I detect GHSA-6q9v-4hq6-5m67 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-6q9v-4hq6-5m67 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.

How does O3 Security protect against GHSA-6q9v-4hq6-5m67?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6q9v-4hq6-5m67 can be triaged on real exposure rather than presence alone.

Is GHSA-6q9v-4hq6-5m67 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6q9v-4hq6-5m67 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-6q9v-4hq6-5m67 published, and has it been updated?

GHSA-6q9v-4hq6-5m67 was published on May 15, 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

GHSA-6q9v-4hq6-5m67 — doctrine/orm

GHSA-6q9v-4hq6-5m67 is a security vulnerability in doctrine/orm. A fix is available for doctrine/orm — see the affected versions and patch details below.

Doctrine SQL injection vulnerability

Published

May 15, 2024

Updated

May 15, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of May 15, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘doctrine/orm🐘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

Affected versions are:

1.2.3 and earlier for PostgreSQL and DB2 Dialects
2.0.2 and earlier

The security issue was found to affect the Doctrine\DBAL\Platforms\AbstractPlatform::modifyLimitQuery() function which does not cast input values for limit and offset to integer and allows malicious SQL to be executed if these parameters are passed into Doctrine 2 directly from request variables without previous cast to integer. Functionality building on top using limit queries in the ORM such as Doctrine\ORM\Query::setFirstResult() and Doctrine\ORM\Query::setMaxResults() are also affected by this security issue.

The fix for this security issue breaks backwards compatibility for developers that extend the Doctrine\DBAL\Platforms\AbstractPlatform::modifyLimitQuery() method, because it is now marked as final. Please overwrite the Doctrine\DBAL\Platforms\AbstractPlatform::doModifyLimitQuery() method instead.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`doctrine/orm`	≥ 2.0.0&&< 2.0.3	2.0.3`composer require doctrine/orm:^2.0.3`
🐘Packagist	`doctrine/orm`	≥ 1.0.0&&< 1.2.4	1.2.4`composer require doctrine/orm:^1.2.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.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6q9v-4hq6-5m67 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6q9v-4hq6-5m67 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6q9v-4hq6-5m67. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Doctrine is prone to SQL injection vulnerability. Users of Doctrine 1.2 and 2 should update to the newly released versions of both libraries immediately. Both versions only include the security fix and no other changes to their previous versions 1.2.3 and 2.0.2. Affected versions are: - 1.2.3 and earlier for PostgreSQL and DB2 Dialects - 2.0.2 and earlier The security issue was found to affect the `Doctrine\DBAL\Platforms\AbstractPlatform::modifyLimitQuery()` function which does not cast input values for limit and offset to integer and allows malicious SQL to be executed if these parameters

O3 Security · Impact-Aware SCA

Is GHSA-6q9v-4hq6-5m67 in your dependencies?

O3 Security finds GHSA-6q9v-4hq6-5m67 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works