Is there a patch available for CVE-2026-8337?

Yes, a patch is available for CVE-2026-8337. Update the affected software to the latest version immediately.

Concrete CMS CVE-2026-8337

Q: What is the CVSS score of CVE-2026-8337?

CVE-2026-8337 has a CVSS 4.0 base score of 6.3 (Medium). CVSS 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:X. EPSS exploitation probability: 0.1%.

EUVD-2026-31359 MEDIUM

Authorization Bypass Through User-Controlled Key (CWE-639)

2026-05-21 ConcreteCMS

GHSA-8c7c-h7px-267g

Authentication Bypass Concrete Cms

6.3

CVSS 4.0 · Vendor: ConcreteCMS

Severity by source

Vendor (ConcreteCMS) PRIMARY

6.3 MEDIUM

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:X

Primary rating from Vendor (ConcreteCMS) · only source for this CVE.

CVSS VectorVendor: ConcreteCMS

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

May 21, 2026 - 22:45 vuln.today

DescriptionCVE.org

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 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

AnalysisAI

Insecure Direct Object Reference (IDOR) in Concrete CMS versions up to and including 9.5.0 enables unauthenticated remote attackers to cast fraudulent votes in restricted private surveys by submitting a private survey's optionID through the publicly accessible voting endpoint. The vulnerability is configuration-dependent - exploitation requires the target site to simultaneously host both public and private surveys - which the CVSS v4.0 vector encodes as AT:P (Attack Requirements: Present), moderately lowering the practical risk surface compared to a universally exploitable flaw. No public exploit code or active exploitation has been identified at time of analysis. Impact is limited to integrity: survey result manipulation with no confidentiality or availability consequence.

Technical ContextAI

Concrete CMS is a PHP-based content management system (CPE: cpe:2.3:a:concrete_cms:concrete_cms:*:*:*:*:*:*:*:*). The vulnerability is classified as CWE-639: Authorization Bypass Through User-Controlled Key - a subclass of IDOR where the application uses a caller-supplied identifier (here, an optionID representing a survey choice) to retrieve or act on a data object without verifying that the caller is authorized to access that specific object. The survey module exposes a public endpoint for submitting votes, but fails to validate that the submitted optionID belongs to the survey associated with that endpoint. Because optionIDs for both public and private surveys share the same namespace or are otherwise reachable, an attacker can cross-reference objects across access boundaries. The CVSS v4.0 score of 6.3 (Medium) reflects network delivery, low complexity once prerequisites are met, no required privileges, but constrained impact (VI:L only) and the prerequisite of a mixed public/private survey deployment.

RemediationAI

The primary remediation is upgrading to Concrete CMS 9.5.1, as indicated by the vendor release notes at https://documentation.concretecms.org/9-x/developers/introduction/version-history/951-release-notes. Organizations unable to patch immediately should audit their site configuration and temporarily remove or unpublish private surveys until the upgrade is applied - eliminating the mixed public/private survey configuration removes the exploitable condition entirely as encoded in AT:P. There is no indication of a WAF rule or network-layer control that would reliably mitigate an IDOR of this type, since the attack uses a legitimate, accessible endpoint with a manipulated parameter. Restricting public access to the survey voting endpoint would break legitimate public survey functionality and is not recommended as a long-term workaround.