How severe is GHSA-rcm4-jv5g-wccm?

GHSA-rcm4-jv5g-wccm has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-rcm4-jv5g-wccm?

GHSA-rcm4-jv5g-wccm affects the following packages: zfr/zfr-oauth2-server-module (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-rcm4-jv5g-wccm?

Update zfr/zfr-oauth2-server-module to 0.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rcm4-jv5g-wccm is resolved across your whole dependency graph.

How do I detect GHSA-rcm4-jv5g-wccm in my Packagist dependencies?

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

How do I mitigate GHSA-rcm4-jv5g-wccm 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-rcm4-jv5g-wccm?

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

Is GHSA-rcm4-jv5g-wccm actively exploited in the wild?

No public exploit code has been indexed for GHSA-rcm4-jv5g-wccm 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-rcm4-jv5g-wccm published, and has it been updated?

GHSA-rcm4-jv5g-wccm was published on June 7, 2024 and was last updated on December 4, 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

HIGH severity

GHSA-rcm4-jv5g-wccm — zfr/zfr-oauth2-server-mod…

HIGHFix: zf-fr/zfr-oauth2-server-module@2ca5bb1

GHSA-rcm4-jv5g-wccm is a high-severity (CVSS 7.5) vulnerability in zfr/zfr-oauth2-server-module. A fix is available for zfr/zfr-oauth2-server-module — see the affected versions and patch details below.

zfr authentication adapter did not verify validity of tokens

Published

Jun 7, 2024

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🐘zfr/zfr-oauth2-server-module

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

Previous to @2ca5bb1c2f11537be8f94ca6867d8d69789e744a (release 0.1.2), tokens weren't checked for validity/expiration.

This potentially caused a security issue if expired tokens were not deleted after the expiration time was past, allowing anyone to still use invalidated authentication credentials.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`zfr/zfr-oauth2-server-module`	all versions	0.1.2`composer require zfr/zfr-oauth2-server-module:^0.1.2`

Detection & mitigation playbook

Open-source dependency

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

Tailored to GHSA-rcm4-jv5g-wccm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Previous to @2ca5bb1c2f11537be8f94ca6867d8d69789e744a (release [0.1.2](https://github.com/zf-fr/zfr-oauth2-server-module/tree/0.1.2)), tokens weren't checked for validity/expiration. This potentially caused a security issue if expired tokens were not deleted after the expiration time was past, allowing anyone to still use invalidated authentication credentials.

O3 Security · Impact-Aware SCA

Is GHSA-rcm4-jv5g-wccm in your dependencies?

O3 Security finds GHSA-rcm4-jv5g-wccm 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