# CVE-2026-111616: Oqtane Framework authorization bypass in SettingController

Source: https://junglewise.ai/threats/cve-2026-111616-oqtane-framework-through-10-2-6-contains-an-authorization-bypass  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-16. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-111616 · Severity: medium · CVSS 4.9 · Published 2026-10-16

Oqtane Framework is an open-source web content management system that allows multiple sites to share a single database within a tenant. An administrator of one site can exploit a flaw in the Settings API to read another site's private configuration, including SMTP credentials used for sending emails, without permission on the target site.

Technologies: [Oqtane Framework](https://junglewise.ai/threats/technologies/oqtane-framework-1). Vendors: [Oqtane](https://junglewise.ai/threats/vendors/oqtane).

## Quick answers

**Is CVE-2026-111616 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-111616 being exploited in the wild.

**How severe is CVE-2026-111616?** Medium severity, with a CVSS score of 4.9, published 16 October 2026.

**Which products and versions are affected?** Oqtane Framework through 10.2.6.

**Is there a fix for CVE-2026-111616?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-111616 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-111616?** Check whether you run Oqtane Framework at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The SettingController's Get endpoint fails to validate that a requested entityId belongs to the current site before returning settings. While the IsAuthorized check approves any View read of Site or Role entities without scoping to the current site, and the repository query returns settings filtered only by entityName and entityId without tenant scoping, the vulnerability is compounded by FilterPrivate keying its decision on per-site Admin role membership—allowing an attacker with Admin role on Site A to bypass the private-settings filter when reading Site B's settings. A multi-tenancy bypass exposes sensitive data including SMTPPassword and SMTPClientSecret in cleartext.

## Affected products

- Oqtane Framework through 10.2.6

## Timeline

- 2026-10-16: disclosed

## References

- [https://github.com/oqtane/oqtane.framework/blob/v10.2.6/Oqtane.Server/Controllers/SettingController.cs](https://github.com/oqtane/oqtane.framework/blob/v10.2.6/Oqtane.Server/Controllers/SettingController.cs)
- [https://hackmd.io/@hieuPenguinnn/oqtane-setting-site-cross-site-private-settings-idor](https://hackmd.io/@hieuPenguinnn/oqtane-setting-site-cross-site-private-settings-idor)

## Related threats

- [Oqtane Framework server-side request forgery in UploadFile](https://junglewise.ai/threats/cve-2026-122008-oqtane-framework-before-10-3-0-contains-a-server-side-request)
- [Oqtane Framework broken access control in SettingController](https://junglewise.ai/threats/cve-2026-122007-oqtane-framework-before-10-3-0-contains-a-broken-access-control)