Skip to content
Fencer Intel
medium 6.1

CVE-2014-10065 json

Content Injection in remarkable

published 2018-05-31 8 y ago modified 2026-06-17 4 mo ago also GHSA-f9vc-q3hh-qhfv , EUVD-2020-0620

cvss
6.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 61%
public exploits
0
none known

Summary

Certain input when passed into remarkable before 1.4.1 will bypass the bad protocol check that disallows the javascript: scheme allowing for javascript: url's to be injected into the rendered content.

Patch / fix

  • npm remarkable 1.4.1
  • remarkable_project remarkable 1.4.1

Exploit prediction

0.94% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • nodesecurity.io https://nodesecurity.io/advisories/30 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 6.1 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected packages

ecosystem package affected fixed in
npm remarkable
<1.4.1
1.4.1

Affected products

  • HackerOne remarkable node module

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.