Skip to content

GHSA-x2fp-hj8c-mmxh CVE-2026-8204

Concrete CMS is vulnerable to authorization bypass in the Calendar Event Frontend Dialog

Medium Packagist
Severity
0.0 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
0.21%
Chance of exploitation in the next 30 days. Higher than 11.43% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-639 Authorization Bypass Through User-Controlled Key
Fix
9.5.1
Upgrade concrete5/concrete5 to this version or later

Description

Concrete CMS 9.5.0 and below is vulnerable to authorization Bypass in the Calendar Event Frontend Dialog which can allow cross-calendar data disclosure. A public calendar block can be used as a pivot point to access private calendar data.

Affected versions

Packagist

PackageVulnerableFixed in
concrete5/concrete5
< 9.5.1
9.5.1

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

concrete5/concrete5 Packagist → 9.5.1

composer
composer require concrete5/concrete5:^9.5.1

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack vector
Network
Attack complexity
Low
Attack requirements
Present
Privileges required
None
User interaction
None
Confidentiality (vulnerable system)
Low
Integrity (vulnerable system)
None
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.1 5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Weakness

CWE-639: Authorization Bypass Through User-Controlled Key

The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

How to prevent it
  • Architecture and Design: For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
  • Architecture and Design, Implementation: Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
  • Architecture and Design: Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-g82f-9pw7-773w
Concrete CMS: PHP Object Injection via unserialize() calls
High Also affects concrete5/concrete5
GHSA-52pr-7vmf-2w7x
Concrete CMS is vulnerable to PHP Object Injection via unserialize() calls in the Workflow, Form block, and File/Set components
High Also affects concrete5/concrete5
GHSA-q9fm-mpg8-8jqm
Concrete CMS is vulnerable to Stored XSS via page name in the Atomik theme
Medium Also affects concrete5/concrete5
GHSA-jqvq-gv67-3567
Concrete CMS is vulnerable to IDOR + wrong-authorization-level in the Express association Reorder dialog
Medium Also affects concrete5/concrete5
GHSA-xjg6-5v39-v7fc
Concrete CMS is vulnerable to CSRF via Backend\File::approveVersion
Medium Also affects concrete5/concrete5
GHSA-44q4-354f-c826
Concrete CMS is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/backend/file approveVersion()
Medium Also affects concrete5/concrete5
GHSA-6qjh-p324-694f
Concrete CMS is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/backend/file rescanMultiple()
High Also affects concrete5/concrete5
GHSA-6fxm-r8p3-mx5c
Concrete CMS is vulnerable to Cross Site Request Forgery (CSRF) at concrete/controllers/backend/file rescan()
High Also affects concrete5/concrete5
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor