CVE-2026-18122: Concrete CMS 9.2.0 to 9.5.2 Express REST API list endpoint exposes restricted Express entries via Missing Authorization

Published Sep 11, 2026
·
Updated

Concrete CMS 9.2.0 to 9.5.2 Express REST API list endpoint exposes restricted Express entries via Missing Authorization; the Concrete CMS REST API's Express entry collection endpoint disabled the per-entry view permission check. An OAuth token with read scope for an Express entity could enumerate entries that its user context lacked permission to view, disclosing each entry's public identifier, URL, label, dates, and any attribute or associated-entry data requested via the includes parameter. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 6.0 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N. Thanks riodrwn for reporting.

Affected Software

1 affected component
Concrete CMS Concrete CMS>=9.2.0<=9.5.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Concrete CMS Express REST API to a version that resolves this vulnerability.

    Fixed in 9.5.2
  2. Configuration

    Enable the per-entry view permission check for the Express entry collection endpoint to prevent OAuth tokens with read scope from enumerating restricted Express entries via the list endpoint.

    Concrete CMS REST API (Express entry collection endpoint) per-entry view permission check = enabled

Event History

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

Frequently Asked Questions

1

Who can exploit this issue?

An attacker needs an OAuth token with read scope for the affected Express entity. The token's user context does not need permission to view the individual entries that can be enumerated.

2

What information can be exposed?

The endpoint can disclose each restricted entry's public identifier, URL, label, and dates. It can also disclose attribute or associated-entry data when that data is requested through the includes parameter.

3

Which deployments are affected?

Concrete CMS versions 9.2.0 through 9.5.2 are affected. Exposure is relevant where the REST API Express entry collection endpoint is available and OAuth tokens have read scope for an Express entity.

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