CVE-2026-7887 For Concrete CMS 9.5.0 and below, OAuth 2.0 Authorization-Code Handler Bypasses Account Status

Low 2.3 Published Updated

Suspended or banned users can bypass account status checks to obtain valid API tokens via OAuth in Concrete CMS.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-7887?

CVE-2026-7887 is a low-severity authentication bypass vulnerability in Concretecms Concrete Cms, published on 21 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official 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.

Weakness: CWE-1287

Which versions are affected by CVE-2026-7887?

2 open source packages ship an affected version, including concrete5/concrete5. It affects 1 product.

PackageAffectedFixed in
concrete5/concrete5 PackagistAll versions9.5.1
concrete5/concrete5 PackagistAll versions9.5.1

Products include Concretecms Concrete Cms.

How do I fix CVE-2026-7887?

Upgrade concrete5/concrete5 to 9.5.1 or later.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2026-7887 being exploited?

There is no known exploitation of CVE-2026-7887 in the wild and no public exploit code.

All Concretecms Concrete Cms vulnerabilities

Sources

Also known as GHSA-f54h-78c9-c24h.

Is CVE-2026-7887 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free