Skip to content

GHSA-f55r-8rcv-mqcf CVE-2023-28472

Concrete CMS missing secure cookie parameters

Medium Packagist
Severity
5.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.59%
Chance of exploitation in the next 30 days. Higher than 48.26% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-613 Insufficient Session Expiration
Fix
9.2.0
Upgrade concrete5/concrete5 to this version or later

Description

Concrete CMS (previously concrete5) before 9.2 does not have Secure and HTTP only attributes set for ccmPoll cookies.

Affected versions

Packagist

PackageVulnerableFixed in
concrete5/concrete5
< 9.2.0
9.2.0

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

composer
composer require concrete5/concrete5:^9.2.0

Severity breakdown

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-613: Insufficient Session Expiration

According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."

How to prevent it
  • Implementation: Set sessions/credentials expiration date.

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