This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Typora
Typora versions prior to 1.4.4 fails to properly neutralize JavaScript code, which may result in executing JavaScript code contained in the file when opening a file with the affected product. (2022-12-07, CVE-2022-43668)
Cross Site Scripting (XSS) in Typora v0.9.65 allows attackers to execute arbitrary code via mathjax syntax due to a mathjax configuration error in the mathematical formula blocks. This is a different vulnerability from CVE-2020-18221. (2021-08-19, CVE-2020-18748)
Cross Site Scripting (XSS) in Typora v0.9.65 and earlier allows remote attackers to execute arbitrary code by injecting commands during block rendering of a mathematical formula. (2021-05-26, CVE-2020-18221)
An issue was discovered in Typora 0.9.67. There is an XSS vulnerability that causes Remote Code Execution. (2021-02-05, CVE-2020-18737)
typora through 0.9.63 has XSS, with resultant remote command execution, during block rendering of a mathematical formula. (2019-01-31, CVE-2019-7295)
typora through 0.9.64 has XSS, with resultant remote command execution, during inline rendering of a mathematical formula. (2019-01-31, CVE-2019-7296)
typora through 0.9.9.20.3 beta has XSS, with resultant remote command execution, via the left outline bar. (2019-01-25, CVE-2019-6803)
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>