CVE-2026-85387CWE-613

CVE-2026-85387

High · published September 16, 2026

CVSS v3.1
7.1
EPSS
0%
Percentile
17.0
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
7.1 · HIGH
Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
CVSS v4.0
2.0 · 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
EPSS
0.00261 · 17.0th percentile
Weakness
CWE-613 · Insufficient Session Expiration
Published
2026-09-16T22:17Z
Affected products (1)
ProductVersionsFixed in
concretecms/concrete_cms< 9.5.49.5.4
References (1)
EPSS history
Timeline
  • 18 SEP 04:02Z
    EPSS moved — → 0%
    epss
  • 16 SEP 17:12Z
    Concrete CMS before 9.5.4 allows a deactivated user to retain OAuth-authenticated REST API access
    cvelistv5