CVE-2026-105783: laurent22 joplin · Origin Validation Error
Affects laurent22 joplinSource CVE Database V5
Not known to be exploited · CVSS 8.0 High : upgrade to 3.7.13 soon.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.7.13
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade joplin and laurent22/joplin to 3.7.13.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| laurent22joplin | Affected
| Fixed in
|
GitHublaurent22/joplinpkg:github/laurent22/joplinOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Joplin Desktop to version 3.7.13 or later, where this origin validation issue is fixed. Users should disable the Web Clipper server if not needed. Since the vulnerability is patched, no additional mitigation is required beyond applying the official fix.
Description
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.
References
- github.com/laurent22/joplin/security/advisories/GHSA-9728-v7ww-mxjv (opens in a new tab)
- github.com/laurent22/joplin/pull/16276 (opens in a new tab)
- github.com/laurent22/joplin/commit/27ae5c0d404ee47ad24862cce917dda6eb2930b7 (opens in a new tab)
- github.com/laurent22/joplin/releases/tag/v3.7.13 (opens in a new tab)