Public mode

No access to your tenant or devices. Every item links to its source. What this means

CVE-2026-81921

In Concrete CMS 8.5.3 to 9,5,2, OAuth 2.0 Refresh-Token Grant Bypasses Account Status

CVSS 4.0 2.3 LOWCheck source for fixed versionsKEV status unknown

Original advisory

cve-program · CVE-2026-81921

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-81921

Published

Concrete CMS

https://github.com/concretecms/concretecms

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "Concrete CMS",
                    "product": "Concrete CMS",
                    "collectionURL": "https://github.com/concretecms/concretecms",
                    "repo": "https://github.com/concretecms/concretecms",
                    "versions": [
                        {
                            "status": "affected",
                            "version": "8.5.3",
                            "lessThanOrEqual": "9.5.2",
                            "versionType": "git"
                        }
                    ],
                    "defaultStatus": "unaffected"
                }

Original source record · Cite this exact observation · Complete original publisher JSON