Concrete CMS 8.5.3 through 9.5.2 enabled the OAuth 2.0 refresh-token grant using the unmodified upstream League grant, which issued new access tokens from a valid refresh token without re-checking the associated account's active status. A user who obtained a refresh token while active could therefore continue to mint valid access tokens after being deactivated or suspended (uIsActive=0), so deactivating an account did not revoke its API access. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 2.3 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L. Thanks sh4d0byss for reporting.
References
| Link | Resource |
|---|---|
| https://documentation.concretecms.org/developers/introduction/version-history/953-release-notes | Broken Link |
Configurations
History
18 Sep 2026, 15:29
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:concretecms:concrete_cms:*:*:*:*:*:*:*:* | |
| References | () https://documentation.concretecms.org/developers/introduction/version-history/953-release-notes - Broken Link | |
| First Time |
Concretecms concrete Cms
Concretecms |
|
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 5.4 |
Information
Published : 2026-09-15 19:17
Updated : 2026-09-18 15:29
NVD link : CVE-2026-81921
Mitre link : CVE-2026-81921
CVE.ORG link : CVE-2026-81921
JSON object : View
Products Affected
concretecms
- concrete_cms
CWE
CWE-862
Missing Authorization
