CVE-2026-85387

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

State
Published
Severity
2.0 Low
Published
Sep 16, 2026
Updated
Sep 17, 2026
Reserved
Sep 3, 2026

Read the record on cve.org

Description

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.

Scores

CVSSScoreVectorSource
4.02.0 LowCVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NConcreteCMS

Weaknesses

  • CWE-613 Insufficient Session Expiration

Affected Products

ProductVersions
Concrete CMSConcrete CMS
  • 5.0.0 through 9.5.3Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.