Concrete CMS Security Fixes with 9.3.3 and 8.5.18

Concrete CMS Security Fixes with 9.3.3 and 8.5.18


Aug 8, 2024
by lisan

Thanks so much to all the community members who report vulnerabilities following the process outlined on https://www.concretecms.org/security and https://hackerone.com/concretecms?type=team so that they can be triaged and remediated by the Concrete Team!

Concrete now displays a more generic error message in RSS Displayer block if curl is unable to load posts. Thanks m3dium for recommending this!

Concrete v.9.3.3 now enforces the Secure Flag for the CONCRETE cookie if a login request is using https by default. This is in line with industry best practice. If a site is served over http:// and the guest uses http:// to log in, the CONCRETE cookie will not have the Secure flag applied so that the site is usable. Although the patch could not be applied cleanly to version 8, the Secure Flag setting can be configured via the dashboard. Since this is a configuration setting, we did not issue a CVE. Thanks Yusuke Uchida for reporting!

As part of our commitment to extend support to Concrete CMS version 8.5 through 2024, we backport security fixes into Concrete 8.5. As the Concrete CMC CVE Certificate Naming Authority (CNA), we have issued the following new Concrete CMS CVEs in conjunction with releases 9.3.3 and 8.5.18:  

Affecting both version 9 and 8: 

The following CVEs do not affect Concrete CMS versions below version 9.