Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 18 Sep 2026 04:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Concretecms
Concretecms concrete Cms |
|
| Vendors & Products |
Concretecms
Concretecms concrete Cms |
Thu, 17 Sep 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 16 Sep 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Concrete CMS before 9.5.4 allows a deactivated user to retain OAuth-authenticated REST API access | |
| Weaknesses | CWE-613 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: ConcreteCMS
Published:
Updated: 2026-09-17T17:32:47.476Z
Reserved: 2026-09-03T18:09:33.097Z
Link: CVE-2026-85387
Updated: 2026-09-17T17:32:43.414Z
Status : Undergoing Analysis
Published: 2026-09-16T18:17:17.850
Modified: 2026-09-17T18:17:11.907
Link: CVE-2026-85387
No data.
OpenCVE Enrichment
Updated: 2026-09-18T04:00:03Z
-
CWE-613
Insufficient Session Expiration