# CVE-2025-69993: Cross-site scripting in n/a

> Attackers can inject arbitrary JavaScript into Leaflet map popups, executing code in the victim's browser session.

- **Severity:** Medium 6.1 (`CVSS:3.1/AC:L/AV:N/A:N/C:L/I:L/PR:N/S:C/UI:R`)
- **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:** 14 Apr 2026
- **Updated:** 21 Apr 2026
- **Also known as:** DEBIAN-CVE-2025-69993, GHSA-h5cx-hfj5-x8v3, UBUNTU-CVE-2025-69993

## What is CVE-2025-69993?

CVE-2025-69993 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Apr 2026. 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

Leaflet versions up to and including 1.9.4 are vulnerable to Cross-Site Scripting (XSS) via the bindPopup() method. This method renders user-supplied input as raw HTML without sanitization, allowing attackers to inject arbitrary JavaScript code through event handler attributes (e.g., <img src=x onerror="alert('XSS')">). When a victim views an affected map popup, the malicious script executes in the context of the victim's browser session.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Leafletjs Leaflet.

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

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

## Is CVE-2025-69993 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69993 exists.

Public exploit code:

- https://github.com/PierfrancescoConti/leaflet-cve-2025-69993 (github_poc): https://github.com/PierfrancescoConti/leaflet-cve-2025-69993

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69993 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69993 exists.

Affected product: n/a. 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-69993/ (Markdown: https://insights.sbomify.com/CVE-2025-69993/index.md)
```

## Sources

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

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