CVE-2025-24028: Cross-site Scripting (XSS) in Rich Text Editor allows arbitrary code execution in Joplin

Published Feb 7, 2025
·
Updated

Joplin is a free, open source note taking and to-do application, which can handle a large number of notes organised into notebooks. This vulnerability is caused by differences between how Joplin's HTML sanitizer handles comments and how the browser handles comments. This affects both the Rich Text Editor and the Markdown viewer. However, unlike the Rich Text Editor, the Markdown viewer is `cross-origin isolated`, which prevents JavaScript from directly accessing functions/variables in the toplevel Joplin `window`. This issue is not present in Joplin 3.1.24 and may have been introduced in `9b50539`. This is an XSS vulnerability that impacts users that open untrusted notes in the Rich Text Editor. This vulnerability has been addressed in version 3.2.12 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

Affected Software

2 affected components
Joplin Joplin>3.1.24, <3.2.12
Joplin Project Joplin<3.2.12

Event History

Feb 7, 2025
CVE Published
via MITRE·10:23 PM
Data Sourced
via MITRE·10:23 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:15 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-24028?

CVE-2025-24028 has been classified with a medium severity level.

2

How do I fix CVE-2025-24028?

To fix CVE-2025-24028, you should update Joplin to version 3.2.12 or later.

3

What versions of Joplin are affected by CVE-2025-24028?

CVE-2025-24028 affects Joplin versions from 3.1.24 up to, but not including, 3.2.12.

4

What impact does CVE-2025-24028 have on users?

CVE-2025-24028 can lead to a potential security risk due to improper handling of HTML comments.

5

Is there a way to mitigate the risk of CVE-2025-24028 without updating?

Currently, the best way to mitigate the risk of CVE-2025-24028 is to apply the latest updates as there are no effective workarounds.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203