CVE-2026-7886: Concrete CMS 9.5.0 and below is vulnerable to IDOR in AddMessage/UpdateMessage via attachments[] parameter

Published May 21, 2026
·
Updated

Concrete CMS 9.5.0 and below is vulnerable to IDOR in AddMessage/UpdateMessage via attachments[] parameter which can lead to file permission bypass. The AddMessage and UpdateMessage conversation controllers accept user-supplied file attachment IDs and load files directly via $em->find(File::class, $attachmentID) without checking per-file permissions (canViewFile()). A user who can post in any conversation can reference any file in the CMS file manager by its sequential ID, effectively bypassing the file permission system.  The Concrete CMS security team gave this vulnerability a CVSS v.4.0 score of 2.3 with a vector CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N. Thanks Tristan Mandani for reporting. if a site truly has private files, the owner should set up a private storage location https://documentation.concretecms.org/user-guide/editors-reference/dashboard/system-and-maintenance/files/file-storage-locations outside of the webroot so that permissions can be checked on view as well. That way, even if a authorized user attaches a file, or otherwise links to it, unauthorized users won't be able to view the file.

Affected Software

2 affected components
Concrete CMS Concrete CMS<=9.5.0
ConcreteCMS Concrete CMS<9.5.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Concrete CMS to a version that resolves this vulnerability.

    Fixed in 9.5.0
  2. Configuration

    Ensure private files are stored using a private storage location outside the webroot so that view-time permission checks can be enforced.

    Concrete CMS file storage locations private storage location (outside of the webroot) = Use a private storage location outside of the webroot so that permissions can be checked on view as well

Event History

May 21, 2026
CVE Published
via MITRE·09:18 PM
Data Sourced
via MITRE·09:18 PM
DescriptionWeakness
Data Sourced
via NVD·10:16 PM
DescriptionSeverityWeaknessAffected Software
Jun 23, 58372
Event
via FIRST·09:13 AM

Frequently Asked Questions

1

What is the severity of CVE-2026-7886?

CVE-2026-7886 has a low severity rating of 2.3 on the CVSS scale.

2

How does CVE-2026-7886 affect Concrete CMS?

CVE-2026-7886 allows for an Insecure Direct Object Reference (IDOR) which can lead to file permission bypass in Concrete CMS.

3

How do I fix CVE-2026-7886?

To fix CVE-2026-7886, it is recommended to upgrade to Concrete CMS version 9.5.1 or later.

4

What versions of Concrete CMS are impacted by CVE-2026-7886?

Concrete CMS versions 9.5.0 and below are impacted by CVE-2026-7886.

5

What does IDOR mean in the context of CVE-2026-7886?

In the context of CVE-2026-7886, IDOR refers to an Insecure Direct Object Reference which allows attackers to access unauthorized files.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203