# CVE-2025-13132: Dia: Increased Spoof Risk; Missing full screen toast

> Attackers can spoof UI elements by entering fullscreen without notification, misleading users about the active site in the Dia browser.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Nov 2025
- **Updated:** 21 Nov 2025
- **Also known as:** GHSA-p3v4-vvf3-w2hh

## What is CVE-2025-13132?

CVE-2025-13132 is a high-severity vulnerability in The Browser Company of New York Dia, published on 21 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.)

Weakness: CWE-1021 (Improper Restriction of Rendered UI Layers or Frames)

## Which versions are affected by CVE-2025-13132?


## How do I fix CVE-2025-13132?

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

## Is CVE-2025-13132 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13132 and fix it if it is affected.

What it is: CVE-2025-13132 is a high-severity vulnerability in The Browser Company of New York Dia, published on 21 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-13132 in the wild and no public exploit code.

Affected product: The Browser Company of New York Dia. 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-2025-13132/ (Markdown: https://insights.sbomify.com/CVE-2025-13132/index.md)
```

## Sources

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

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