NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

Joplin vulnerable to Cross-site Scripting in notesGHSA-mrmf-755g-w2vw

MEDIUMFix: laurent22/joplin@feaecf7

GHSA-mrmf-755g-w2vw is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in joplin. A fix is available for joplin — see the affected versions and patch details below.

Also known asCVE-2021-37916
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk
0.00%0.41%0.82%1.23%0.4%0.7%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

3other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
joplinnpm
3Kdownloads / week

Description

Joplin before 2.0.9 allows Cross-site Scripting via button and form in the note body.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmjoplinall versions2.0.9npm install joplin@2.0.9

Affected Products

1 product · 1 configurations
Application
joplinjoplin_project
< 2.0.9
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for joplin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update joplin to 2.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mrmf-755g-w2vw is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Joplin before 2.0.9 allows Cross-site Scripting via button and form in the note body.
O3 Security · Impact-Aware SCA

Is GHSA-mrmf-755g-w2vw in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Joplin vulnerable to Cross-site Scripting in notes