Is CVE-2026-8415 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-8415 being exploited in the wild.

How severe is CVE-2026-8415?

Medium severity, with a CVSS score of 4, published 21 May 2026.

Which products and versions are affected?

Concrete CMS 9.0.0 to 9.4.8, 9.0.0RC1 to 9.5.0; concrete5/concrete5 (Packagist) >= 9.0.0RC1, < 9.5.1, ECOSYSTEM:introduced=9.0.0RC1,fixed=9.5.1.

Is there a fix for CVE-2026-8415?

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-8415 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-8415?

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.

CVE-2026-8415: Concrete CMS CSRF in Express association reordering

Q: Is there a fix for CVE-2026-8415?

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.

Q: How is CVE-2026-8415 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-8415?

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.

CVE-2026-8415 · Severity: medium · CVSS 4 · Published 2026-05-21

Concrete CMS, a popular content management system, is vulnerable to a security flaw that could allow an attacker to trick an administrator into performing unintended actions. Specifically, an attacker could force a logged-in user to reorder data associations within the system without their consent. While this does not directly expose sensitive data, it can disrupt site organization and data integrity if a user is successfully deceived into clicking a malicious link.

Technologies: Concrete CMS, concrete5/concrete5 (Packagist). Vendors: Concrete CMS, Packagist.

Quick answers

Is CVE-2026-8415 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-8415 being exploited in the wild.
How severe is CVE-2026-8415?: Medium severity, with a CVSS score of 4, published 21 May 2026.
Which products and versions are affected?: Concrete CMS 9.0.0 to 9.4.8, 9.0.0RC1 to 9.5.0; concrete5/concrete5 (Packagist) >= 9.0.0RC1, < 9.5.1, ECOSYSTEM:introduced=9.0.0RC1,fixed=9.5.1.
Is there a fix for CVE-2026-8415?: 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-8415 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-8415?: 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

A Cross-Site Request Forgery (CSRF) vulnerability exists in Concrete CMS versions 9.0.0RC1 through 9.5.0. The flaw is located in the 'concrete/controllers/dialog/express/association/reorder' controller, which fails to properly validate CSRF tokens before processing reordering requests. An attacker can exploit this by inducing a logged-in administrator to visit a malicious webpage or click a crafted link, leading to unauthorized changes in Express data associations. The vulnerability is mitigated by the requirement for user interaction and the specific nature of the affected component. The issue is addressed in version 9.5.1.

Affected products

Concrete CMS Concrete CMS 9.0.0RC1 to 9.5.0

Identifiers

CVE-2026-8415
GHSA-xj25-753j-wgp9

Timeline

2026-05-21: disclosed: NVD publication date
2026-05-22: advisory: GitHub Advisory published
2026-06-24: patched: Advisory updated with patch information

References

https://documentation.concretecms.org/9-x/developers/introduction/version-history/951-release-notes

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.