CVE-2015-3296 json
NodeBB Cross-site Scripting Vulnerability in Markdown Processing
published 2017-09-21 9 y ago modified 2026-09-10 1 mo ago also GHSA-9g4f-5rpg-4948 , EUVD-2022-3370
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 69%
- public exploits
- 0
- none known
Summary
Multiple cross-site scripting (XSS) vulnerabilities in NodeBB before 0.7 allow remote attackers to inject arbitrary web script or HTML via vectors related to (1) javascript: or (2) data: URLs.
Patch / fix
- npm nodebb 0.70
- npm nodebb-plugin-markdown 5.1.1
Exploit prediction
1.26% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).
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 |
| GitHub | 3.0 | 6.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | nodebb | <0.70 |
0.70 |
| npm | nodebb-plugin-markdown | <5.1.1 |
5.1.1 |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/julianlam/nodebb-plugin-markdown/commit/ab7f2684750882f7baefbfa31db8d5aac71e6ec3
patch, third-party-advisory
-
openwall.com
/lists/oss-security/2015/04/10/10
mailing-list, web, patch, third-party-advisory
-
github.com
/NodeBB/nodebb-plugin-markdown/commit/ab7f2684750882f7baefbfa31db8d5aac71e6ec3
web
-
github.com
/markdown-it/markdown-it/commit/f76d3beb46abd121892a2e2e5c78376354c214e3
web
-
securityfocus.com
/bid/71824
vdb-entry, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2015-3296
advisory
-
github.com
/NodeBB/NodeBB/issues/2273
web
-
web.archive.org
/web/20200228230630/http://www.securityfocus.com/bid/71824
web
Sources
- CVE List CVE-2015-3296
- GitHub Advisory GHSA-9g4f-5rpg-4948
- NVD CVE-2015-3296
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.