Concrete CMS below 9.5.3 does not perform an object-level authorization check when a Page Type was updated. (CVE-2026-81915)
Concrete CMS versions below 9.5.3 have a vulnerability where object-level authorization checks are not performed when updating a Page Type. This allows a signed-in dashboard user with permission to edit one Page Type to modify other Page Types outside their authorization scope. The vulnerability arises because the update_page_type token is action- and user-scoped but not object-scoped, failing to restrict which Page Type can be targeted.
AI Analysis
Technical Summary
Concrete CMS prior to version 9.5.3 does not enforce object-level authorization when a Page Type is updated. The Types::submit() dashboard controller loads and saves the Page Type identified by a user-supplied ptID without invoking the canEditPageType() check. Consequently, a dashboard user authorized to edit a single Page Type can alter configurations of other Page Types beyond their assigned permissions. The update_page_type token validation is insufficient as it is scoped to the action and user, not the specific object, allowing unauthorized modifications. The vulnerability is tracked as CVE-2026-81915 and has a CVSS v4.0 base score of 5.1.
Potential Impact
An authenticated dashboard user with permission to edit at least one Page Type can exploit this vulnerability to modify other Page Types outside their authorization boundary. This could lead to unauthorized configuration changes within the CMS, potentially impacting site behavior or security controls tied to Page Types. There is no indication of remote unauthenticated exploitation or privilege escalation beyond the dashboard user’s existing permissions.
Mitigation Recommendations
Upgrade Concrete CMS to version 9.5.3 or later, where this vulnerability has been addressed by adding proper object-level authorization checks when updating Page Types. No other mitigation or workaround is indicated. Patch status is not explicitly stated in the input, but the version 9.5.3 is referenced as the fixed version, so updating to 9.5.3 or newer is recommended.
Concrete CMS below 9.5.3 does not perform an object-level authorization check when a Page Type was updated. (CVE-2026-81915)
Description
Concrete CMS versions below 9.5.3 have a vulnerability where object-level authorization checks are not performed when updating a Page Type. This allows a signed-in dashboard user with permission to edit one Page Type to modify other Page Types outside their authorization scope. The vulnerability arises because the update_page_type token is action- and user-scoped but not object-scoped, failing to restrict which Page Type can be targeted.
CVSS v4.0
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Concrete CMS prior to version 9.5.3 does not enforce object-level authorization when a Page Type is updated. The Types::submit() dashboard controller loads and saves the Page Type identified by a user-supplied ptID without invoking the canEditPageType() check. Consequently, a dashboard user authorized to edit a single Page Type can alter configurations of other Page Types beyond their assigned permissions. The update_page_type token validation is insufficient as it is scoped to the action and user, not the specific object, allowing unauthorized modifications. The vulnerability is tracked as CVE-2026-81915 and has a CVSS v4.0 base score of 5.1.
Potential Impact
An authenticated dashboard user with permission to edit at least one Page Type can exploit this vulnerability to modify other Page Types outside their authorization boundary. This could lead to unauthorized configuration changes within the CMS, potentially impacting site behavior or security controls tied to Page Types. There is no indication of remote unauthenticated exploitation or privilege escalation beyond the dashboard user’s existing permissions.
Mitigation Recommendations
Upgrade Concrete CMS to version 9.5.3 or later, where this vulnerability has been addressed by adding proper object-level authorization checks when updating Page Types. No other mitigation or workaround is indicated. Patch status is not explicitly stated in the input, but the version 9.5.3 is referenced as the fixed version, so updating to 9.5.3 or newer is recommended.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-jv42-fxrq-qxjp
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-81915"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6aa4a02655bf5e2cf5a869c4
Added to database: 09/12/2026, 00:43:18 UTC
Last enriched: 09/12/2026, 01:18:15 UTC
Last updated: 09/12/2026, 01:18:15 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.