CVE-2026-7886: Concrete CMS is vulnerable to IDOR in AddMessage/UpdateMessage
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()).
Published May 22, 2026 · Updated Jun 24, 2026
Affected packages
concrete5/concrete5
- Ecosystem
- Composer (PHP)
- Affected
- < 9.5.1
- Fixed in
- 9.5.1
- Check
composer show concrete5/concrete5
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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. 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 an authorized user attaches a file, or otherwise links to it, unauthorized users won't be able to view the file.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-10721
Concrete CMS: PHP Object Injection via unserialize() calls
high8.4Jun 10, 2026CVE-2026-7888
Concrete CMS is vulnerable to PHP Object Injection via unserialize() calls in the Workflow, Form block, and File/Set components
high8.4Jun 3, 2026CVE-2026-8340
Concrete CMS is vulnerable to CSRF via Backend\File::approveVersion
low2.3May 26, 2026CVE-2026-8347
Concrete CMS is vulnerable to IDOR + wrong-authorization-level in the Express association Reorder dialog
low2.3May 26, 2026CVE-2026-8353
Concrete CMS is vulnerable to Stored XSS via page name in the Atomik theme
low2.1May 26, 2026CVE-2026-7879
Concrete CMS has an unauthorized file access issue
medium6.3May 22, 2026
