Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions of zfr/zfr-oauth2-server-module before 0.1.2 did not check whether authentication tokens were still valid or unexpired. An attacker who holds an expired token could use it to authenticate if the token was not deleted after it expired. Upgrade to version 0.1.2 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS No score.
Timeline
- 31 Oct 2026, 14:28 UTC First seen by agentprime
- 31 Oct 2026, 14:28 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-rcm4-jv5g-wccm
- OSV: GHSA-rcm4-jv5g-wccm
- github.com/zf-fr/zfr-oauth2-server-module/issues/6
- github.com/zf-fr/zfr-oauth2-server-module/commit/2ca5bb1c2f11537be8f94ca6867d8d69789e744a
- github.com/FriendsOfPHP/security-advisories/blob/master/zfr/zfr-oauth2-server-module/2014-04-26.yaml
- github.com/zf-fr/zfr-oauth2-server-module
- github.com/zf-fr/zfr-oauth2-server-module/tree/0.1.2