CVE-2026-8337
Access Control in Concretecms Concrete Cms ≤ 9.5.1
Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/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:XSummary
CVE-2026-8337 is a medium-severity Reliance on Cookies without Validation and Integrity Checking (CWE-565) vulnerability in Concretecms Concrete Cms. Its CVSS base score is 6.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Web Session Cookie (T1550.004); ranked at the 9th 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 AC-24 (Access Control Decisions) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-31359
Vulnerability Data
Concrete CMS 9.5.0 and below is vulnerable to IDOR in surveys. To be vulnerable, a site would have to be configured in such a way that both public and private surveys are present on the site. An unauthenticated attacker can…
more
vote in the restricted survey by submitting the restricted optionID through the public survey’s endpoint. The Concrete CMS security team gave this vulnerability a CVSS v.4.0 score of 6.3 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N. Thanks Zer0daySec https://github.com/Zee99y for reporting
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Enforcing approved authorizations on every access request structurally stops a user-controlled key from reaching another user's data.
Requiring explicit access-control decisions on each request blocks unauthorized key-driven access.
Session Authenticity directly requires protecting the integrity and authenticity of session tokens such as cookies, eliminating blind reliance on them.
Least-privilege restrictions limit the scope of data reachable even if a key check is bypassed.
Transmission Confidentiality and Integrity mandates cryptographic or equivalent protection for data in transit, which covers cookie values exchanged over HTTP.
Software, Firmware, and Information Integrity can detect unauthorized modification of cookie-based data after the fact via integrity verification.
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.
Cookies commonly carry identity assertions; requiring their protection, conveyance, and verification directly eliminates the weakness.
Enforcing authorization policy and least privilege directly blocks user-controlled key tampering that bypasses access checks.
Strong authentication mechanisms reduce reliance on unvalidated cookies for identity and access decisions.
Cryptographic integrity for data-in-transit directly mitigates tampering of cookies sent over the network.
Logical access controls prevent unauthorized data access that results from missing authorization checks on object references.
Integrity protections for data-at-rest can apply to cookie stores but do not cover validation during use.
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.
Security testing can detect cookie-validation flaws but does not itself implement the required controls.
Information access restriction explicitly enforces that users may only retrieve data they are authorized to see, directly addressing user-controlled key bypass.
Access control policy directly requires enforcement of authorization rules that prevent unauthorized access via manipulated keys.
Managing access rights includes ensuring users can only access their own records and not bypass authorization by altering identifiers.
Privileged access rights control restricts what data each user may access, mitigating direct object reference attacks.
Secure development lifecycle includes authorization design but does not itself implement runtime access checks.