# CVE-2026-122007: Oqtane Framework before 10.3.0 Broken Access Control via SettingController


- **Severity:** High 7.4 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 8 Nov 2026
- **Also known as:** GHSA-mq53-5f2v-2rj6

## What is CVE-2026-122007?

CVE-2026-122007 is a high-severity vulnerability in oqtane.framework, published on 4 Nov 2026. 

### Official description

Oqtane Framework before 10.3.0 contains a broken access control vulnerability in SettingController.cs that allows an authenticated site administrator to read and modify settings belonging to other sites within the same tenant database by supplying an arbitrary entityId for Site or Role type settings, since IsAuthorized and FilterPrivate fail to verify the requested site matches the current alias SiteId. Attackers can exploit the /api/setting endpoints to disclose private values such as SMTPPassword, SMTPClientSecret, and ExternalLogin ClientSecret, and to alter another site's OIDC/OAuth2 authentication configuration without requiring host privileges.

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

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


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

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

## Is CVE-2026-122007 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122007 is a high-severity vulnerability in oqtane.framework, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-122007 in the wild and no public exploit code.

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

## Sources

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

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