How severe is GHSA-6wqp-7g94-f69j?

GHSA-6wqp-7g94-f69j has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-6wqp-7g94-f69j?

GHSA-6wqp-7g94-f69j affects the following packages: sensiolabs/connect (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-6wqp-7g94-f69j?

Update sensiolabs/connect to 4.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6wqp-7g94-f69j is resolved across your whole dependency graph.

How do I detect GHSA-6wqp-7g94-f69j in my Packagist dependencies?

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

How do I mitigate GHSA-6wqp-7g94-f69j 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-6wqp-7g94-f69j?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6wqp-7g94-f69j can be triaged on real exposure rather than presence alone.

Is GHSA-6wqp-7g94-f69j actively exploited in the wild?

No public exploit code has been indexed for GHSA-6wqp-7g94-f69j 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-6wqp-7g94-f69j published, and has it been updated?

GHSA-6wqp-7g94-f69j was published on May 21, 2024 and was last updated on December 6, 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

MEDIUM severity

GHSA-6wqp-7g94-f69j — sensiolabs/connect

MEDIUMFix: sensiolabs/connect#63

GHSA-6wqp-7g94-f69j is a medium-severity (CVSS 6.1) vulnerability in sensiolabs/connect. A fix is available for sensiolabs/connect — see the affected versions and patch details below.

sensiolabs/connect has a Cross-Site Request Forgery Vulnerability

Published

May 21, 2024

Updated

Dec 6, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 6, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘sensiolabs/connect

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

Versions of sensiolabs/connect prior to 4.2.3 are affected by a Cross-Site Request Forgery (CSRF) vulnerability due to the absence of the state parameter in OAuth requests. The lack of proper state parameter handling exposes applications to CSRF attacks during the OAuth authentication flow.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`sensiolabs/connect`	all versions	4.2.3`composer require sensiolabs/connect:^4.2.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sensiolabs/connect, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sensiolabs/connect to 4.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6wqp-7g94-f69j 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-6wqp-7g94-f69j can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6wqp-7g94-f69j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-6wqp-7g94-f69j in your dependencies?

O3 Security finds GHSA-6wqp-7g94-f69j 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