Vulnerability Database · npm · gitbook · Version
gitbook 2.3.3
2.3.3 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 2.6.9.
Critical 0 High 0 Medium 2 Low 0 Unrated 0
-
Released 10 Sep 2015
Status deprecated release
Licence Apache-2.0
Also known from other sources 2
Newer releases 136
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
gitbook 2.3.3 vulnerabilities
2 vulnerabilities cover gitbook 2.3.3. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2017-16019: Cross-Site Scripting in gitbook | 6.1 medium | 3.2.2 | 01 Sep 2020 |
| CVE-2019-19596: Cross-site Scripting in GitBook | 5.4 medium | No fix published | 24 May 2022 |
Looking for another version, or everything Vulert holds for gitbook?
Questions
About gitbook 2.3.3
Is gitbook 2.3.3 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover gitbook 2.3.3: 0 critical, 0 high, 2 medium and 0 low. The upgrade Vulert recommends is 2.6.9, and each entry above names the fixed version to move to.
Which version of gitbook should I use instead of 2.3.3?
2.6.9 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 2.3.3 the latest release of gitbook?
No. 2.3.3 was published 10 Sep 2015, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor gitbook for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the gitbook version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.