Joplin is an open source note-taking and to-do application that organises notes and lists into notebooks. Prior to 3.7.13, when Joplin Desktop is running with the opt-in Web Clipper server enabled, the server in packages/lib/ClipperServer.ts sends Access-Control-Allow-Origin: * and allows an arbitrary website to call POST /auth and GET /auth/check because the pairing endpoints do not reject HTTP or HTTPS origins. The desktop confirmation dialog does not identify the requesting origin, so a victim who approves the generic prompt authorizes the attacking page, which then receives the permanent API token. The token provides ongoing read and write access to notes, folders, tags, resources, and master keys. This issue is fixed in version 3.7.13.
CVE-2026-105783
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 8.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-92870 (ENISA EUVD)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.0
- EG Score
- 8.0HIGHmedium confidence
- EG Risk
- 36EG Risk 36/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity80% × 45%Impact severity (EG Severity): CVSS 8.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.1% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.1%
- EPSS %ILE
- 3rd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.0): severity, escalated by confirmed exploitation. This CVE's 8.0 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 5, 2026
Last Modified
October 6, 2026
Advisory Details (4)
Auto-updated Oct 5, 2026v3.7.13
Patch available: laurent22/joplin v3.7.13 (pre-release)
https://github.com/laurent22/joplin/releases/tag/v3.7.13commit 27ae5c0d404e (laurent22/joplin)
Fix landed in laurent22/joplin commit 27ae5c0d404e — awaiting tagged release
https://github.com/laurent22/joplin/commit/27ae5c0d404ee47ad24862cce917dda6eb2930b7Desktop: Restrict Web Clipper pairing to extension origins
Fix merged in laurent22/joplin PR #16276 on 2026-08-22 — awaiting tagged release
https://github.com/laurent22/joplin/pull/16276Any website open in the browser can trigger and win Joplin's Web Clipper pairing dialog, stealing the permanent full-access API token, because the local server has no Origin/Referer restriction and the confirmation dialog shows no identifying information · Advisory · laurent22/joplin · GitHub
https://github.com/laurent22/joplin/security/advisories/GHSA-9728-v7ww-mxjvWeakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 43× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-11-01 08:12 UTCEG score recompute
- 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-25 14:55 UTCEG score recompute
- 2026-10-25 01:51 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-18 05:08 UTCEG score recompute
- 2026-10-17 19:33 UTCEG score recompute
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-12 16:39 UTCEG score recompute
Show 18 moreShow fewer
- 2026-10-11 20:15 UTCEG score recompute
- 2026-10-11 17:03 UTCEG score recompute
- 2026-10-11 15:01 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-11 06:01 UTCEG score recompute
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-09 20:56 UTCEG score recompute
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-08 22:51 UTCEG score recompute
- 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-08 00:36 UTCEG score recompute
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-06 15:32 UTCEG score recompute
- 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
- 2026-10-06 14:55 UTCEG score recompute
- 2026-10-06 00:26 UTCEG score recompute
- 2026-10-05 23:27 UTCEG score recomputeFirst assessed: 8.0 HIGH
- 2026-10-05 23:25 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-105783?
When was the CVE record for CVE-2026-105783 published?
Is CVE-2026-105783 actively exploited?
What is the CVSS score of CVE-2026-105783?
How do I remediate CVE-2026-105783?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-105783
Is Your Infrastructure Affected by CVE-2026-105783?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.