Signal is active with 2 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
For Concrete CMS 9.5.0 and below, OAuth 2.0 Authorization-Code Handler Bypasses Account Status. A user with uIsActive=0 (suspended, banned, terminated employee) can still authenticate via OAuth and receive valid API tokens. The Concrete CMS security team gave this vulnerability a CVSS v.4.0 score of 2.3 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N. Thanks 0x4c616e for reporting.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
NONE
Momentum
NONE
If you run products in this scope, you should treat this CVE as relevant to your environment.
CVE-2026-7887 For Concrete CMS 9.5.0 and below, OAuth 2.0 Authorization-Code Handler Bypasses Account Status. A user with uIsActive=0 (suspended, banned, terminated employee) can sti… https://www.cve.org/CVERecord?id=CVE-2026-7887
Post summary
Concrete CMS versions 9.5.0 and below suffer an OAuth 2.0 Authorization‑Code Handler flaw that lets users flagged as inactive (uIsActive=0) bypass account status checks and authenticate.
🚨*CVE* CVE-2026-7887 For Concrete CMS 9.5.0 and below, OAuth 2.0 Authorization-Code Handler Bypasses Account Status. A user with uIsActive=0 (suspended, banned, terminated employee) can sti… https://www.cve.org/CVERecord?id=CVE-2026-7887 ----- Traducción: CVE-2026-7887 Par… http://infoflow.cloud`
Post summary
The tweet reports CVE‑2026‑7887 with a concise vulnerability statement for Concrete CMS, but offers no PoC, exploit code, active exploitation evidence, or mitigation guidance.
1 of 1 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| App | concretecms | concrete_cms | - | - | - |