Concrete CMS before 9.5.4 allows a deactivated user to retain OAuth-authenticated REST API access
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-85387
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 04:07 UTC · Revision 1
Source evidence
Concrete CMS before 9.5.4 allows a deactivated user to retain OAuth-authenticated REST API access
core-osv · Original sourcePublished 16 Sept 2026, 17:12 UTC
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.
osv:CVE-2026-85387
Complete source record
{
"id": "3663141e329f63fc1621f467eebc45ad47d658ac58325734d2d2101fe9a3b3fe",
"url": "https://osv.dev/vulnerability/CVE-2026-85387",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Concrete CMS before 9.5.4 allows a deactivated user to retain OAuth-authenticated REST API access",
"summary": "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.",
"evidence": "osv:CVE-2026-85387",
"products": [],
"severity": "low",
"structured": {
"id": "CVE-2026-85387",
"aliases": [
"CVE-2026-85387"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/concretecms/concretecms",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "66d3f3d614e26e4b7955b967fed133a8acdb6820"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "5.0.0"
},
{
"last_affected": "9.5.3"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"cpe": "cpe:2.3:a:concretecms:concrete_cms:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "9.5.4"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"9.5.3",
"9.5.2",
"9.5.1",
"9.5.0",
"9.5.0RC2",
"9.5.0RC1",
"9.4.4",
"9.4.3",
"9.4.2",
"9.4.1",
"9.4.0",
"9.4.0RC2",
"9.4.0RC1",
"9.3.7",
"9.3.6",
"9.3.5",
"9.3.0",
"9.3.4",
"9.3.3",
"9.3.2",
"9.3.1",
"8.4.1",
"8.3.1",
"8.2.1",
"8.2.0",
"8.2.0RC2",
"8.1.0",
"5.7.5.7",
"5.7.5.6",
"5.7.5.5",
"5.7.5.2",
"5.7.4.1",
"5.7.3.1",
"5.7.3",
"5.7.2.1",
"5.7.2",
"5.7.0.4",
"5.7.1",
"5.7.0.3",
"5.7.0.1",
"5.7.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-85387.json"
}
}
],
"modified": "2026-10-28T02:30:42.273649732Z",
"provider": "osv",
"references": [
"https://documentation.concretecms.org/developers/introduction/version-history/954-release-notes",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/85xxx/CVE-2026-85387.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-85387",
"https://github.com/concretecms/concretecms"
],
"provider_metadata": {
"cwe_ids": [
"CWE-613"
],
"cna_assigner": "ConcreteCMS",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/85xxx/CVE-2026-85387.json"
}
},
"related_cves": [
{
"value": "CVE-2026-85387",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 510133,
"published_at": "2026-09-16T17:12:05.336+00:00"
}