Vulnerability Database · npm · jsreport · Version
jsreport 1.9.2
1.9.2 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 1 High 1 Medium 0 Low 0 Unrated 0
-
Released 16 Nov 2017
Licence non-standard
Also known from other sources 2
Newer releases 153
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
jsreport 1.9.2 vulnerabilities
2 vulnerabilities cover jsreport 1.9.2. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2023-2583: Code Injection Vulnerability in jsreport | 10.0 critical | 3.11.3 | 08 May 2023 |
| CVE-2020-8128: Server-Side Request Forgery and Inclusion of Functionality from Untrusted Control Sphere in jsreport | 9.8 high | 2.6.0 | 13 Apr 2021 |
Looking for another version, or everything Vulert holds for jsreport?
Questions
About jsreport 1.9.2
Is jsreport 1.9.2 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover jsreport 1.9.2: 1 critical, 1 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 1.9.2 the latest release of jsreport?
No. 1.9.2 was published 16 Nov 2017, 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 jsreport for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the jsreport version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.