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

> Authenticated dashboard users can modify unauthorized Page Type configurations due to missing object-level authorization checks in Concrete CMS.

- **Severity:** Medium 5.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-jv42-fxrq-qxjp

## What is CVE-2026-81915?

CVE-2026-81915 is a medium-severity missing authorization vulnerability in Concretecms Concrete Cms, published on 11 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-81915?

It affects 1 product.


Products: Concretecms Concrete Cms.

## How do I fix CVE-2026-81915?

No fix has been published for CVE-2026-81915 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-81915 being exploited?

There is no known exploitation of CVE-2026-81915 in the wild and no public exploit code.

## Other vulnerabilities in Concretecms Concrete Cms

- [CVE-2023-48648](https://insights.sbomify.com/CVE-2023-48648/): Concrete CMS allows unauthorized access because directories can be created with insecure permissions (critical 9.8)
- [CVE-2022-21829](https://insights.sbomify.com/CVE-2022-21829/): Code injection in concrete CMS (critical 9.8)
- [CVE-2021-22958](https://insights.sbomify.com/CVE-2021-22958/): Server-Side Request Forgery vulnerability in concrete5 (critical 9.8)
- [CVE-2021-40098](https://insights.sbomify.com/CVE-2021-40098/): Path traversal in n/a (critical 9.8)
- [CVE-2026-8134](https://insights.sbomify.com/CVE-2026-8134/): Concrete CMS Vulnerable to Relative Path Traversal (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81915 and fix it if it is affected.

What it is: CVE-2026-81915 is a medium-severity missing authorization vulnerability in Concretecms Concrete Cms, published on 11 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-81915 in the wild and no public exploit code.

Affected product: Concretecms Concrete Cms. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-81915/ (Markdown: https://insights.sbomify.com/CVE-2026-81915/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-81915
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-81915
- OSV: https://osv.dev/vulnerability/CVE-2026-81915

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-81915/
Summaries are generated and may contain mistakes; the official description above is the record.