Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

GHSA-phj8-2p6x-hq5r — joplin

MEDIUMFix: laurent22/joplin@9c20d59

GHSA-phj8-2p6x-hq5r is a medium-severity (CVSS 5.4) vulnerability in joplin. 1 public exploit reference exists, so weaponization risk is real. A fix is available for joplin — see the affected versions and patch details below.

Joplin Cross Site Scripting Vulnerability via NOSCRIPT tags

Also known asCVE-2021-33295
Published
Jun 17, 2022
Updated
Apr 23, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Sep 27, 2026 · OSV.dev, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-phj8-2p6x-hq5r by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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
2Kdownloads / week

Description

Cross Site Scripting (XSS) vulnerability in Joplin Desktop App before 1.8.5 allows attackers to execute aribrary code due to improper sanitizing of html.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmjoplinall versions1.8.5npm install joplin@1.8.5
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

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 1.8.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-phj8-2p6x-hq5r 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

Cross Site Scripting (XSS) vulnerability in Joplin Desktop App before 1.8.5 allows attackers to execute aribrary code due to improper sanitizing of html.
O3 Security · Impact-Aware SCA

Is GHSA-phj8-2p6x-hq5r in your dependencies?

Find it across npm, including transitive dependencies.