Concrete CMS 8.5.3 through 9.5.2 enabled the OAuth 2.0 refresh-token grant using the unmodified upstream League grant
Source GCVE Database
Not known to be exploited · CVSS 5.4 Medium.
Data as of 31 Oct 2026, 20:20 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.
What to do
AI-suggested
Until a fix is available, organizations should consider additional controls around refresh token issuance and account deactivation processes to mitigate risk.
Description
Concrete CMS versions 8.5.3 through 9.5.2 use an unmodified OAuth 2.0 refresh-token grant implementation that does not verify if an account is active when issuing new access tokens. This allows a user with a valid refresh token obtained while active to continue generating access tokens even after their account is deactivated or suspended, effectively bypassing account deactivation for API access. The vulnerability has a low CVSS v4.0 score of 2.3.