CVE-2026-81915: In Concrete CMS below 9.5.3, Page Type update omits object-level authorization

Published Sep 11, 2026
·
Updated

Concrete CMS below 9.5.3 does not perform an object-level authorization check when a Page Type was updated. The Types::submit() dashboard controller loaded and saved the Page Type identified by a user-supplied ptID without calling canEditPageType(), so a signed-in dashboard user permitted to edit one Page Type could modify the configuration of Page Types outside their assigned authorization boundary. The updatepagetype token was validated but is action- and user-scoped rather than object-scoped, so it did not constrain which Page Type could be targeted. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 5.1 with vector CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N. Thanks Andrew Gonzalez for reporting.

Affected Software

1 affected component
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
  2. Compensating control

    Restrict dashboard access so only users within the intended authorization boundary can submit Page Type updates (because Types::submit() can update Page Types identified by a user-supplied ptID without calling canEditPageType()).

Event History

Sep 11, 2026
CVE Published
via MITRE·07:39 PM
Data Sourced
via MITRE·07:39 PM
DescriptionWeakness

Frequently Asked Questions

1

What access would an attacker need to exploit this issue?

The attacker must be signed in as a dashboard user and already have permission to edit at least one Page Type. They can then target another Page Type by supplying its ptID during an update request.

2

What can be modified if the issue is exploited?

An authorized Page Type editor can modify the configuration of Page Types outside their assigned authorization boundary. The issue affects the integrity of Page Type configuration; the provided CVSS vector indicates no confidentiality or availability impact.

3

Does the update request token prevent this attack?

No. The update_page_type token is scoped to the action and user, but not to the specific Page Type object, so it does not restrict which ptID can be targeted.

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