CVE-2026-85387

published 16 Sep 2026 · updated 17 Sep 2026

Concrete CMS before 9.5.4 allows a deactivated user to retain OAuth-authenticated REST API access

2.0LowCVSS 2.0EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

Concrete CMS before 9.5.4 re-authorized OAuth REST API requests from the bearer token alone and did not re-check the state of the account the token had been issued to. The resource server's authorization validator confirmed only that a token existed, had not expired, and had not been explicitly revoked, and deactivating a user did not revoke that user's outstanding tokens. As a result, a deactivated user retained full access to /ccm/api/1.0/* for the remaining lifetime of any token already issued to them. The same gap applied to accounts that had been deleted or locked pending a forced password reset. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 2.0 with vector CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N. Thanks Myq Larson for reporting.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Concrete CMS>=5.0.0 <=9.5.3

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-85387 severity on Zeptric[![CVE-2026-85387](https://zeptric.io/badge/cve/CVE-2026-85387.svg)](https://zeptric.io/cve/CVE-2026-85387)