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 update_page_type 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.
References
| Link | Resource |
|---|---|
| https://documentation.concretecms.org/developers/introduction/version-history/953-release-notes | Broken Link |
Configurations
History
24 Sep 2026, 20:07
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:concretecms:concrete_cms:*:*:*:*:*:*:*:* | |
| First Time |
Concretecms
Concretecms concrete Cms |
|
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 5.3 |
| References | () https://documentation.concretecms.org/developers/introduction/version-history/953-release-notes - Broken Link |
Information
Published : 2026-09-11 20:19
Updated : 2026-09-24 20:07
NVD link : CVE-2026-81915
Mitre link : CVE-2026-81915
CVE.ORG link : CVE-2026-81915
JSON object : View
Products Affected
concretecms
- concrete_cms
