Read the docs

Broken access control in Oqtane Framework settings API exposes other sites

Priority LOW 35CWE-639Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-639.

Summary

Oqtane Framework before 10.3.0 contains a broken access control flaw in SettingController that lets an authenticated site administrator read and modify settings belonging to other sites in the same tenant database. The flaw, tracked as CWE-639, arises because the requested entityId for Site or Role settings is not checked against the current site. An attacker with site administrator access can use the /api/setting endpoints to read private values such as SMTP passwords and client secrets and to change another site's OIDC or OAuth2 authentication configuration, without host privileges.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00383 32nd percentileScored 2026-11-07
Fix Fixed oqtane.framework (oqtane): 10.3.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
oqtaneoqtane.framework1.0.0 to before 10.3.010.3.0Patch availableCNA
  • oqtane.framework Vendoroqtane Affected 1.0.0 to before 10.3.0 Fixed in 10.3.0 Patch available CNA

Remediation

Update oqtane.framework to version 10.3.0, which fixes the issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

  • Fix · CNA oqtane.framework (oqtane) Fixed in 10.3.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    oqtane.framework 10.3.0

    2 records Highest priority Priority LOW 2 LOW

    Other records, highest priority first

    • TI-2026-85079 Server-side request forgery in Oqtane Framework file upload from URLPriority LOW 24

Timeline

  1. 2026-11-04 Threatist record created from CVE-2026-122007
  2. 2026-11-04 Alias added: GHSA-mq53-5f2v-2rj6
  3. 2026-11-04 CISA SSVC decision points changed
  4. 2026-11-04 Priority changed: MEDIUM → LOW

References

  • TI-2026-75402 Authorization bypass in Oqtane exposes other sites' SMTP secrets CVSS 4.0MEDIUM 6.9
  • TI-2026-85079 Server-side request forgery in Oqtane Framework file upload from URL CVSS 4.0MEDIUM 5.3

Sources