{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-105783 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-105783 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-105783 is a high-severity vulnerability in laurent22 joplin, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-105783 and fix it if it is affected.\n\nWhat it is: CVE-2026-105783 is a high-severity vulnerability in laurent22 joplin, published on 5 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-105783 in the wild and no public exploit code.\n\nAffected product: laurent22 joplin. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-105783/ (Markdown: https://insights.sbomify.com/CVE-2026-105783/index.md)","id":"CVE-2026-105783","markdown":"https://insights.sbomify.com/CVE-2026-105783/index.md","name":"CVE-2026-105783","record":{"aliases":["GHSA-9728-v7ww-mxjv"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Joplin note-taking app","requires_auth":"none","summary":"Attackers can steal permanent API tokens via cross-origin requests if the Web Clipper server is enabled, granting full access to user notes.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"},{"id":"CWE-346","name":"Origin Validation Error"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Joplin Web Clipper pairing allows cross-origin theft of a permanent API token","id":"CVE-2026-105783","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Joplin whiteboard card rendering allows CSS injection into application chrome","id":"CVE-2026-105784"},"packages":[],"prev":{"headline":"Scrapy: Arbitrary Module Import via Referrer-Policy Header in RefererMiddleware","id":"CVE-2026-105782"},"products":["joplin"],"published":"2026-10-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-06","vendors":["laurent22"]},"summary":"Attackers can steal permanent API tokens via cross-origin requests if the Web Clipper server is enabled, granting full access to user notes.","url":"https://insights.sbomify.com/CVE-2026-105783/"}