CVE Vulnerabilities

CVE-2026-12323

Improper Restriction of Rendered UI Layers or Frames

Published: Jun 16, 2026 | Modified: Jun 17, 2026
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
3.4 LOW
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

Spoofing issue in the DOM: Core & HTML component. This vulnerability was fixed in Firefox 152 and Thunderbird 152.

Weakness

The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain.

Affected Software

NameVendorStart VersionEnd Version
FirefoxMozilla*152.0.0 (excluding)
ThunderbirdMozilla*152.0.0 (excluding)
Mozjs102Ubuntuesm-apps/noble*
Mozjs102Ubuntujammy*
Mozjs102Ubuntunoble*
Mozjs115Ubuntunoble*
Mozjs52Ubuntuesm-apps/focal*
Mozjs52Ubuntuesm-infra/bionic*
Mozjs68Ubuntuesm-infra/focal*
Mozjs78Ubuntuesm-apps/jammy*
Mozjs78Ubuntujammy*
Mozjs91Ubuntujammy*
ThunderbirdUbuntujammy*

Potential Mitigations

  • The use of X-Frame-Options allows developers of web content to restrict the usage of their application within the form of overlays, frames, or iFrames. The developer can indicate from which domains can frame the content.
  • The concept of X-Frame-Options is well documented, but implementation of this protection mechanism is in development to cover gaps. There is a need for allowing frames from multiple domains.
  • A developer can use a “frame-breaker” script in each page that should not be framed. This is very helpful for legacy browsers that do not support X-Frame-Options security feature previously mentioned.
  • It is also important to note that this tactic has been circumvented or bypassed. Improper usage of frames can persist in the web application through nested frames. The “frame-breaking” script does not intuitively account for multiple nested frames that can be presented to the user.

References