Quick answers
- Is CVE-2026-8239 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-8239 being exploited in the wild.
- How severe is CVE-2026-8239?
- Medium severity, with a CVSS score of 4, published 21 May 2026.
- Which products and versions are affected?
- Concrete CMS <= 9.5.0, 9.5.0 and below; concrete5/concrete5 (Packagist) < 9.5.1, ECOSYSTEM:introduced=0,fixed=9.5.1.
- Is there a fix for CVE-2026-8239?
- Yes. concrete5/concrete5 (Packagist): upgrade to 9.5.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-8239 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-8239?
- Check whether you run Concrete CMS or concrete5/concrete5 (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- concrete5/concrete5 (Packagist): upgrade to 9.5.1 or later
composer require concrete5/concrete5:^9.5.1
Technical details
An Insecure Direct Object Reference (IDOR) vulnerability exists in Concrete CMS versions 9.5.0 and below due to missing authorization checks in the '/ccm/frontend/conversations/get_rating' endpoint. An unauthenticated attacker can send network requests to this endpoint with arbitrary message IDs to confirm the existence of messages and retrieve their associated rating scores. This occurs because the application fails to verify if the requester has the appropriate permissions to access the metadata of the specified message object. The issue is addressed in version 9.5.1.
Affected products
- Concrete CMS Concrete CMS <= 9.5.0
Identifiers
- CVE-2026-8239
- GHSA-2xp7-rpvc-pjwc
Timeline
- 2026-05-21: disclosed: NVD publication date
- 2026-05-22: advisory: GitHub Advisory published
- 2026-06-24: patched: Advisory updated with patch information