What is GHSA-RCM4-JV5G-WCCM?

GHSA-RCM4-JV5G-WCCM is a high-severity security vulnerability in zfr/zfr-oauth2-server-module (composer), affecting versions < 0.1.2. It is fixed in 0.1.2.

How severe is GHSA-RCM4-JV5G-WCCM?

GHSA-RCM4-JV5G-WCCM has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of zfr/zfr-oauth2-server-module are affected by GHSA-RCM4-JV5G-WCCM?

zfr/zfr-oauth2-server-module (composer) versions < 0.1.2 is affected.

Is there a fix for GHSA-RCM4-JV5G-WCCM?

Yes. GHSA-RCM4-JV5G-WCCM is fixed in 0.1.2. Upgrade to this version or later.

Is GHSA-RCM4-JV5G-WCCM exploitable, and should I be worried?

Whether GHSA-RCM4-JV5G-WCCM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-RCM4-JV5G-WCCM is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-RCM4-JV5G-WCCM in zfr/zfr-oauth2-server-module

Q: How severe is GHSA-RCM4-JV5G-WCCM?

GHSA-RCM4-JV5G-WCCM has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of zfr/zfr-oauth2-server-module are affected by GHSA-RCM4-JV5G-WCCM?

zfr/zfr-oauth2-server-module (composer) versions < 0.1.2 is affected.

Q: Is there a fix for GHSA-RCM4-JV5G-WCCM?

Yes. GHSA-RCM4-JV5G-WCCM is fixed in 0.1.2. Upgrade to this version or later.

Q: Is GHSA-RCM4-JV5G-WCCM exploitable, and should I be worried?

Whether GHSA-RCM4-JV5G-WCCM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-RCM4-JV5G-WCCM is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-RCM4-JV5G-WCCM?

Upgrade zfr/zfr-oauth2-server-module to 0.1.2 or later.

Summary

zfr authentication adapter did not verify validity of tokens

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.

Impact

GHSA-RCM4-JV5G-WCCM has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.1.2); upgrading removes the vulnerable code path.

Affected versions

zfr/zfr-oauth2-server-module (< 0.1.2)

Security releases

zfr/zfr-oauth2-server-module → 0.1.2 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade zfr/zfr-oauth2-server-module to 0.1.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-RCM4-JV5G-WCCM? GHSA-RCM4-JV5G-WCCM is a high-severity security vulnerability in zfr/zfr-oauth2-server-module (composer), affecting versions < 0.1.2. It is fixed in 0.1.2.
How severe is GHSA-RCM4-JV5G-WCCM? GHSA-RCM4-JV5G-WCCM has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of zfr/zfr-oauth2-server-module are affected by GHSA-RCM4-JV5G-WCCM? zfr/zfr-oauth2-server-module (composer) versions < 0.1.2 is affected.
Is there a fix for GHSA-RCM4-JV5G-WCCM? Yes. GHSA-RCM4-JV5G-WCCM is fixed in 0.1.2. Upgrade to this version or later.
Is GHSA-RCM4-JV5G-WCCM exploitable, and should I be worried? Whether GHSA-RCM4-JV5G-WCCM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-RCM4-JV5G-WCCM is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-RCM4-JV5G-WCCM? Upgrade zfr/zfr-oauth2-server-module to 0.1.2 or later.