CVE-2021-39175 json
XSS vector in slide mode speaker-view
published 5y ago modified 4mo ago also EUVD-2021-25572
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 49%
- public exploits
- 0
- none known
Summary
HedgeDoc is a platform to write and share markdown. In versions prior to 1.9.0, an unauthenticated attacker can inject arbitrary JavaScript into the speaker-notes of the slide-mode feature by embedding an iframe hosting the malicious code into the slides or by embedding the HedgeDoc instance into another page. The problem is patched in version 1.9.0. There are no known workarounds aside from upgrading.
Patch / fix
- hedgedoc hedgedoc 1.9.0
- hedgedoc Arch Linux 1.9.0-1
arch linux advisories AVG-2331
- github.com/hedgedoc/hedgedoc#1369 pull request
- github.com/hedgedoc/hedgedoc#1375 pull request
- github.com/hedgedoc/hedgedoc#1513 pull request
- github.com/hedgedoc/hedgedoc/security/advisories/GHSA-j748-779h-9697 advisory
Is CVE-2021-39175 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.60% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
| NVD | 3.1 | 6.1 | CVSS:3.1/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 products
- hedgedoc hedgedoc
Classification
References
-
github.com
/hedgedoc/hedgedoc/pull/1369
patch, third-party-advisory
-
github.com
/hedgedoc/hedgedoc/pull/1375
patch, third-party-advisory
-
github.com
/hedgedoc/hedgedoc/pull/1513
patch, third-party-advisory
-
github.com
/hedgedoc/hedgedoc/security/advisories/GHSA-j748-779h-9697
patch, third-party-advisory
Sources
- CVE List CVE-2021-39175
- NVD CVE-2021-39175
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.