# CVE-2025-25187: Cross-site Scripting in Goto Anything allows arbitrary code execution in Joplin

> Attackers can execute arbitrary code via XSS in Joplin's search feature due to unsanitized HTML and enabled node integration.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Feb 2025
- **Updated:** 10 Feb 2025
- **Also known as:** GHSA-9gfv-q6wj-fr3c

## What is CVE-2025-25187?

CVE-2025-25187 is a high-severity cross-site scripting vulnerability in laurent22 joplin, published on 7 Feb 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Joplin is a free, open source note taking and to-do application, which can handle a large number of notes organised into notebooks. This vulnerability is caused by adding note titles to the document using React's `dangerouslySetInnerHTML`, without first escaping HTML entities. Joplin lacks a Content-Security-Policy with a restrictive `script-src`. This allows arbitrary JavaScript execution via inline `onclick`/`onload` event handlers in unsanitized HTML. Additionally, Joplin's main window is created with `nodeIntegration` set to `true`, allowing arbitrary JavaScript execution to result in arbitrary code execution. Anyone who 1) receives notes from unknown sources and 2) uses <kbd>ctrl</kbd>-<kbd>p</kbd> to search is impacted. This issue has been addressed in version 3.1.24 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

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

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

It affects 1 product.


Products: Joplin Project Joplin.

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

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

## Is CVE-2025-25187 being exploited?

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

## Other vulnerabilities in laurent22 joplin

- [CVE-2022-23340](https://insights.sbomify.com/CVE-2022-23340/): Joplin Vulnerable to Code Injection (critical 9.8)
- [CVE-2024-40643](https://insights.sbomify.com/CVE-2024-40643/): Joplin has a parsing error leading to Cross-site Scripting (XSS) (critical 9.7)
- [CVE-2023-45673](https://insights.sbomify.com/CVE-2023-45673/): Arbitrary code execution on click of PDF links in Joplin (high 8.9)
- [CVE-2025-27134](https://insights.sbomify.com/CVE-2025-27134/): Privilege escalation in Joplin server via user patch endpoint (high 8.8)
- [CVE-2023-37898](https://insights.sbomify.com/CVE-2023-37898/): Safe mode Cross-site Scripting (XSS) vulnerability in Joplin (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25187 is a high-severity cross-site scripting vulnerability in laurent22 joplin, published on 7 Feb 2025. It can only be exploited from the same machine or local network, 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-25187 exists.

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

## Sources

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

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