Quick answers
- Is CVE-2026-8347 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-8347 being exploited in the wild.
- How severe is CVE-2026-8347?
- Medium severity, with a CVSS score of 4.3, published 22 May 2026.
- Which products and versions are affected?
- Concrete CMS <= 9.5.0, 5.0 to 9.5.0; concrete5/concrete5 (Packagist) < 9.5.1, ECOSYSTEM:introduced=0,fixed=9.5.1.
- Is there a fix for CVE-2026-8347?
- 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-8347 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-8347?
- 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
Concrete CMS versions 9.5.0 and below contain an Insecure Direct Object Reference (IDOR) and improper authorization level check within the Express association Reorder dialog. An authenticated attacker with low-level 'view-only' permissions can exploit this flaw to reorder Express entities, a task that should require higher administrative privileges. This results in cross-entity state tampering. The vulnerability specifically affects sites utilizing the Express component and relying on entity ordering. The issue is addressed in version 9.5.1.
Affected products
- Concrete CMS Concrete CMS 5.0 to 9.5.0
Identifiers
- CVE-2026-8347
- GHSA-jqvq-gv67-3567
Timeline
- 2026-05-22: advisory: NVD and Vendor advisory published
- 2026-05-22: patched: Fixed in version 9.5.1 release notes