VYPR
Low severityNVD Advisory· Published May 21, 2026

CVE-2026-8416

CVE-2026-8416

Description

Concrete CMS 9 before 9.5.0 is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/backend/file addFavoriteFolder($id). 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:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N. Thanks Yonatan Drori (Tenzai) for reporting.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Concrete CMS 9 before 9.5.0 is vulnerable to CSRF in the addFavoriteFolder endpoint, allowing an attacker to add a favorite folder on behalf of a logged-in user.

Vulnerability

CVE-2026-8416 is a Cross-Site Request Forgery (CSRF) vulnerability in Concrete CMS versions 9 prior to 9.5.0. The flaw exists in the addFavoriteFolder action of the concrete/controllers/backend/file controller. The root cause is the lack of CSRF protection on this specific endpoint, enabling an attacker to forge requests that add a folder to the user's favorites without their consent [1].

Exploitation

To exploit this vulnerability, an attacker needs to trick an authenticated Concrete CMS user into visiting a malicious page or clicking a crafted link. The attacker does not require any special privileges on the target system; the victim must be logged in to the CMS for the CSRF request to succeed. The attack can be launched from any network location, as the request is sent to the legitimate server by the victim's browser. The CVSS v4.0 vector indicates low attack complexity and no required privileges, but a passive attacker profile (AT:P) suggests the attacker must rely on user interaction [1].

Impact

A successful CSRF attack could cause the targeted user's session to add a file folder to their favorites list. The impact is considered low, as the action only modifies the user's personal preferences (favorites) and does not affect other users or system configuration. The CVSS v4.0 confidentiality, integrity, and availability scores are all low or none, reflecting that this is a limited, non-escalating issue [1].

Mitigation

The vulnerability is fixed in Concrete CMS version 9.5.0, which was released alongside the 9.5.1 release notes. Users running Concrete CMS 9 should upgrade to version 9.5.0 or later to eliminate the CSRF risk. No workarounds are documented, but applying the update is straightforward via Composer or direct file replacement [1].

AI Insight generated on May 21, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

1

News mentions

0

No linked articles in our index yet.