Content Injection in remarkable
Versions 1.4.0 and earlier of remarkable are affected by a cross-site scripting vulnerability. This occurs because vulnerable versions of remarkable did not properly whitelist link protocols, and consequently allowed javascript: to be used.
Proof of Concept
Markdown Source:
[link](<javascript:alert(1)>)Rendered HTML:
<a href="javascript:alert(1)">link</a>Recommendation
Update to version 1.4.1 or later
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | remarkable | < 1.4.1 | 1.4.1 |
References
- Weakness (CWE)
CWE-94- Platform
- npm
- Package
remarkable- Disclosed
- 31.08.2020
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-f9vc-q3hh-qhfv - CC BY 4.0
Vulnerability history: remarkable
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 4
- First → latest
- 11.2018 08.2020
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- High 3
- Medium 1
Disclosures per year
- 2018: 1
- 2019: 2
- 2020: 1
- 2021: 0
- 2022: 0
- 2023: 0
- 2024: 0
- 2025: 0
- 2026: 0
-
Content Injection in remarkable this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.