Cyber Resilience

CVE-2026-8433

CSRF in Concretecms Concrete Cms 9.0.0 – 9.5.1

Published
21 May 2026
Modified
23 July 2026
CVSS Score v4 2.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0013 3th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2026-8433 is a low-severity CSRF (CWE-352) vulnerability in Concretecms Concrete Cms. Its CVSS base score is 2.3 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Concrete CMS 9 before 9.5.0 is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/backend/file rescan(). 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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-8413Same product: Concretecms Concrete Cms
CVE-2026-8414Same product: Concretecms Concrete Cms
CVE-2026-8412Same product: Concretecms Concrete Cms
CVE-2026-8416Same product: Concretecms Concrete Cms
CVE-2026-8415Same product: Concretecms Concrete Cms
CVE-2026-8435Same product: Concretecms Concrete Cms
CVE-2026-8410Same product: Concretecms Concrete Cms
CVE-2026-8411Same product: Concretecms Concrete Cms
CVE-2026-8432Same product: Concretecms Concrete Cms
CVE-2026-8434Same product: Concretecms Concrete Cms

Affected Assets

concretecms
concrete cms
9.0.0 — 9.5.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V3.3.2
  • V3.5.1
  • V10.2.1

Mitigating Controls (NIST 800-53 r5) AI

Establishing secure configuration settings for web components includes requiring appropriate SameSite attributes on sensitive cookies.

Proper SameSite settings on session cookies directly help protect the authenticity of communications sessions against cross-site misuse.

Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-01 mostly match
prevents

Secure configuration baselines and enforcement directly require proper SameSite settings on sensitive cookies.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect missing SameSite attributes but does not prevent the weakness.

mitigates

By denying access to phishing or malicious sites, the control lowers the likelihood that a user will be tricked into submitting a forged request that performs an unintended action on another site.

prevents

Application security requirements can mandate SameSite attributes on sensitive cookies.

prevents

Secure coding standards directly require proper SameSite settings to prevent CSRF.

none

Contextual intelligence about emerging CSRF toolkits can be translated into updated anti-CSRF token or same-site policy configurations across applications.

References