CVE-2026-18120: Missing Authorization in legacy Express entries search endpoint allows disclosure of Express entry data

Published Sep 16, 2026
·
Updated

Concrete CMS before 9.5.3 exposed a legacy Express entry search endpoint that returned entry result JSON without invoking the canViewExpressEntries() permission check applied by the normal dashboard and CSV Export flow. An unauthenticated visitor who knew or discovered an Express entity identifier could enumerate that entity's entry search results, disclosing attribute values intended to be restricted to privileged users. For Express entities that do not support entry-specific permissions (i.e., supportsEntrySpecificPermissions() returns false), per-entry permission filtering is additionally disabled via EntryList::ignorePermissions(). The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 6.3 with vector CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N. Thanks Daniel Powell for reporting.

Affected Software

1 affected component
Concrete CMS Concrete CMS<9.5.3

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

Event History

Sep 16, 2026
CVE Published
via MITRE·05:16 PM
Data Sourced
via MITRE·05:16 PM
DescriptionWeakness

Frequently Asked Questions

1

Which deployments are exposed?

Concrete CMS versions before 9.5.3 are affected where legacy Express entry search endpoints are available. Exposure concerns Express entities whose entry search results contain attribute values intended only for privileged users.

2

What does an attacker need to exploit this?

An attacker does not need to authenticate or interact with a user, but must know or discover an Express entity identifier. The CVSS vector also identifies attack complexity as high and attack requirements as present.

3

Are all Express entities filtered the same way?

No. For entities that do not support entry-specific permissions, where supportsEntrySpecificPermissions() returns false, the affected flow additionally disables per-entry filtering through EntryList::ignorePermissions().

4

What version addresses the issue?

Upgrade Concrete CMS to version 9.5.3 or later.

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