CVE-2025-13132VulnerabilityPublished 21 Nov 2025

CVE-2025-13132: The Browser Company of New York Dia · Clickjacking

Affects The Browser Company of New York DiaSource CVE Database V5

Not known to be exploited · CVSS 7.4 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.4High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
The Browser Company of New York Dia	Affected =0	Fixed in–

AI-suggested

European organizations should implement several specific measures to mitigate this vulnerability beyond generic advice. First, restrict or disable fullscreen mode in managed browser environments where possible, using group policies or browser management tools to prevent unauthorized fullscreen activation. Second, deploy endpoint security solutions capable of detecting anomalous UI behaviors or suspicious fullscreen transitions. Third, conduct targeted user awareness training emphasizing the importance of recognizing fullscreen notifications and verifying site authenticity, especially when entering sensitive information. Fourth, monitor network traffic and logs for unusual patterns indicative of phishing or UI spoofing attempts involving the Dia browser. Fifth, encourage users to update to patched versions promptly once available and maintain an inventory of browser versions in use to identify vulnerable endpoints. Sixth, consider deploying browser isolation or sandboxing technologies to contain potential UI spoofing attacks. Finally, collaborate with The Browser Company to obtain timely patches and security advisories. Organizations should also review and enhance their phishing detection and response capabilities to quickly identify and mitigate attacks exploiting this vulnerability.

Description

This vulnerability allowed a site to enter fullscreen, after a user click, without a full-screen notification (toast) appearing. Without this notification, users could potentially be misled about what site they were on if a malicious site renders a fake UI (like a fake address bar.)

Impact

For European organizations, this vulnerability poses a significant risk primarily through social engineering and phishing attacks. Attackers can exploit the lack of fullscreen notifications to create convincing fake interfaces, potentially tricking users into entering sensitive information such as login credentials, financial data, or personal details. This can lead to credential compromise, unauthorized access, and data breaches. Sectors such as finance, government, healthcare, and critical infrastructure are particularly at risk due to the high value of their data and the potential impact of phishing attacks. The vulnerability affects the integrity of the user interface, undermining user trust and increasing the likelihood of successful attacks. Although the vulnerability does not directly impact system availability or confidentiality through technical means, the indirect consequences of successful phishing can be severe. European organizations using the Dia browser, especially in environments where user awareness is low or where the browser is used for sensitive operations, face elevated risk. The absence of a patch increases exposure time, necessitating proactive mitigation. Additionally, attackers could leverage this vulnerability as part of multi-stage attacks, combining UI spoofing with malware delivery or lateral movement within networks.

CWE-1021Improper Restriction of Rendered UI Layers or Frames (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain.
Implementation
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.
Implementation
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.
Implementation
This defense-in-depth technique can be used to prevent the improper usage of frames in web applications. It prioritizes the valid sources of data to be loaded into the application through the usage of declarative policies.
OWASP Cheat Sheets
Content Security Policy (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V14.4.3 (opens in a new tab)
V14.4.7 (opens in a new tab)
Attack patterns
Clickjacking (opens in a new tab)
Flash File Overlay (opens in a new tab)
iFrame Overlay (opens in a new tab)
Task Impersonation (opens in a new tab)
Tapjacking (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

diabrowser.com/security/bulletins (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Nov 2025, 18:14 UTC

WeaknessesCWE-1021

Technical details

References

Community reviews

Related threats