This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Joplin
Joplin v2.8.8 allows attackers to execute arbitrary commands via a crafted payload injected into the Node titles. (2022-07-25, CVE-2022-35131)
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. (2022-06-16, CVE-2021-33295)
Joplin before 2.0.9 allows XSS via button and form in the note body. (2021-08-03, CVE-2021-37916)
Joplin 1.2.6 for Desktop allows XSS via a LINK element in a note. (2020-11-06, CVE-2020-28249)
An XSS issue in Joplin desktop 1.0.190 to 1.0.245 allows arbitrary code execution via a malicious HTML embed tag. (2020-09-24, CVE-2020-15930)
Joplin through 1.0.184 allows Arbitrary File Read via XSS. (2020-02-17, CVE-2020-9038)
Joplin version prior to 1.0.90 contains a XSS evolving into code execution due to enabled nodeIntegration for that particular BrowserWindow instance where XSS was identified from vulnerability in Note content field - information on the fix can be found here https://github.com/laurent22/joplin/commit/494e235e18659574f836f84fcf9f4d4fcdcfcf89 that can result in executing unauthorized code within the rights in which the application is running. This attack appear to be exploitable via Victim synchronizing notes from the cloud services or other note-keeping services which contain malicious code. This vulnerability appears to have been fixed in 1.0.90 and later. (2018-06-26, CVE-2018-1000534)
Why Cross-site Scripting can be dangerous
Cross site scripting is an attack where a web page executes code that is injected by an adversary. It usually appears, when users input is presented. This attack can be used to impersonate a user, take over control of the session, or even steal API keys.
The attack can be executed e.g. when you application injects the request parameter directly into the HTML code of the page returned to the user:
https://server.com/confirmation?message=Transaction+Complete
what results in:
<span>Confirmation: Transaction Complete</span>
In that case the message can be modified to become a valid Javascript code, e.g.:
https://server.com/confirmation?message=<script>dangerous javascript code here</script>
and it will be executed locally by the user's browser with full access to the user's personal application/browser data:
<span>Confirmation: <script>dangerous javascript code here</script></span>