# CVE-2026-68530: Missing authorization in Concrete CMS

> A board editor can access and delete instances of other boards due to missing authorization checks on specific dashboard actions.

- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:L/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:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-58xf-6w56-p6xr

## What is CVE-2026-68530?

CVE-2026-68530 is a low-severity missing authorization vulnerability in Concrete CMS, published on 15 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Concrete CMS 9 through 9.5.2 did not perform an authorization check on several board-instance actions in the Boards area of the Dashboard. The instance details single-page controller resolved a board instance directly from an attacker-supplied instance ID and then viewed, refreshed, regenerated, or deleted it without verifying that the requester held edit_board_settings on the instance's parent board. As a result, a user granted board-edit rights on a single board could reach the instances of any other board on the site by supplying their instance IDs. The affected actions bypassed the controller's permission-checked accessor (the same accessor used by the read view, which runs canEditBoardSettings on the parent board) and validated only an action-scoped CSRF token, which is bound to the action name rather than to the target object and is therefore reusable across boards. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 2.1 with vector CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N. Thanks Winston Crooker for reporting.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-68530 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68530 is a low-severity missing authorization vulnerability in Concrete CMS, published on 15 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-68530 in the wild and no public exploit code.

Affected product: 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-68530/ (Markdown: https://insights.sbomify.com/CVE-2026-68530/index.md)
```

## Sources

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

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