API token issuance via ignored account status
Published May 21, 2026 · Updated May 21, 2026
Authentication bypass in Concrete CMS 9.5.0 and earlier allows remote authenticated users to obtain API tokens through OAuth 2.0. The authorization-code handler issues tokens without checking the matched account’s uIsActive flag, so a value of 0 is ignored. Exploitation requires a disabled account that can complete the configured OAuth flow; granted token scopes bound the accessible API data and actions.
Summary
What happened
Authentication bypass in Concrete CMS 9.5.0 and earlier allows remote authenticated users to obtain API tokens through OAuth 2.0. The authorization-code handler issues tokens without checking the matched account’s uIsActive flag, so a value of 0 is ignored. Exploitation requires a disabled account that can complete the configured OAuth flow; granted token scopes bound the accessible API data and actions.
The record
- CVE
- CVE-2026-7887
- Published
- May 21, 2026
- Updated
- May 21, 2026
- Vendor
- Concrete CMS
- Product
- Concrete CMS
- Classifications
- CWE-1287, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2026CVE publishedPublication date reported by the CVE source.
- May 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.0 <=9.5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo