VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

jsreport: vulnerability history, versions and safety

jsreport is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 96 releases, from Apr 2021 to May 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all jsreport vulnerabilities

Vulert verdict on jsreport 4.14.4 i

Updated on 23 Oct 2026

Good news: 4.14.4, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 71/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 4.14.4 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.14.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.14.4 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 0 in the last year i
  • Latest disclosure 08 May 2023 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i
  • Stars 1,322 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for jsreport, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.14.4 15 Oct 2026 none non-standard — Details →
4.14.3 15 Oct 2026 none non-standard — Details →
4.14.2 11 Sep 2026 none non-standard — Details →
4.14.1 05 Aug 2026 none non-standard — Details →
4.14.0 04 Aug 2026 none non-standard — Details →
4.13.0 29 Apr 2026 none non-standard — Details →
4.12.0 04 Feb 2026 none non-standard — Details →
4.11.0 26 Nov 2025 none non-standard — Details →
4.10.1 13 Aug 2025 none non-standard — Details →
4.10.0 24 Jul 2025 none non-standard — Details →
4.9.0 07 May 2025 none non-standard — Details →
4.8.0 28 Feb 2025 none non-standard — Details →
4.7.0 29 Oct 2024 none non-standard — Details →
4.6.0 13 Aug 2024 none non-standard — Details →
4.5.0 19 Jun 2024 none non-standard — Details →
4.4.0 20 May 2024 none non-standard — Details →
4.3.1 28 Mar 2024 none non-standard — Details →
4.3.0 15 Mar 2024 none non-standard — Details →
4.2.0 07 Dec 2023 none non-standard — Details →
4.1.0 05 Oct 2023 none non-standard — Details →
4.0.0 01 Sep 2023 none non-standard — Details →
3.13.0 16 Jun 2023 none non-standard — Details →
3.12.0 08 Jun 2023 none non-standard — Details →
3.11.3 21 Apr 2023 none non-standard — Details →
3.11.2 05 Apr 2023 C1 non-standard Yes Details →
3.11.1 03 Apr 2023 C1 non-standard Yes Details →
3.11.0 24 Mar 2023 C1 non-standard Yes Details →
3.10.0 09 Jan 2023 C1 non-standard Yes Details →
3.9.0 23 Nov 2022 C1 non-standard Yes Details →
3.8.0 26 Sep 2022 C1 non-standard Yes Details →
3.7.1 05 Aug 2022 C1 non-standard Yes Details →
3.7.0 04 Aug 2022 C1 non-standard Yes Details →
3.6.2 01 Jun 2022 C1 non-standard Yes Details →
3.6.1 27 May 2022 C1 non-standard Yes Details →
3.6.0 25 May 2022 C1 non-standard Yes Details →
3.5.0 04 May 2022 C1 non-standard Yes Details →
3.4.1 15 Feb 2022 C1 non-standard Yes Details →
3.4.0 03 Feb 2022 C1 non-standard Yes Details →
3.3.0 11 Jan 2022 C1 non-standard Yes Details →
3.2.0 17 Dec 2021 C1 non-standard Yes Details →
3.1.1 18 Nov 2021 C1 non-standard Yes Details →
3.1.0 17 Nov 2021 C1 non-standard Yes Details →
3.0.1 26 Oct 2021 C1 non-standard Yes Details →
3.0.0 26 Oct 2021 C1 non-standard Yes Details →
3.0.0-beta.2 20 Aug 2021 C1 non-standard Yes Details →
3.0.0-beta.1 20 Aug 2021 C1 non-standard Yes Details →
2.11.0 07 Dec 2020 C1 non-standard Yes Details →
2.10.0 07 Sep 2020 C1 non-standard Yes Details →
2.9.0 17 Jul 2020 C1 non-standard Yes Details →
2.8.0 20 May 2020 C1 non-standard Yes Details →
2.7.2 20 Mar 2020 C1 non-standard Yes Details →
2.7.1 05 Mar 2020 C1 non-standard Yes Details →
2.7.0 04 Mar 2020 C1 non-standard Yes Details →
2.6.1 09 Oct 2019 C1 non-standard Yes Details →
2.6.0 20 Sep 2019 C1 non-standard Yes Details →
2.5.0 24 May 2019 C1 H1 non-standard Yes Details →
2.4.0 05 Mar 2019 C1 H1 non-standard Yes Details →
2.3.0 11 Dec 2018 C1 H1 non-standard Yes Details →
2.2.0 22 Aug 2018 C1 H1 non-standard Yes Details →
2.1.1 05 Jul 2018 C1 H1 non-standard Yes Details →
2.1.0 31 May 2018 C1 H1 non-standard Yes Details →
2.0.0 11 May 2018 C1 H1 non-standard Yes Details →
2.0.0-beta 28 Mar 2018 C1 H1 non-standard Yes Details →
1.10.0 30 Jan 2018 C1 H1 non-standard Yes Details →
1.9.2 16 Nov 2017 C1 H1 non-standard Yes Details →
1.9.1 08 Nov 2017 C1 H1 non-standard Yes Details →
1.9.0 08 Nov 2017 C1 H1 non-standard Yes Details →
1.8.2 21 Aug 2017 C1 H1 non-standard Yes Details →
1.8.1 11 Aug 2017 C1 H1 non-standard Yes Details →
1.7.0 20 Apr 2017 C1 H1 non-standard Yes Details →
1.6.0 29 Mar 2017 C1 H1 non-standard Yes Details →
1.5.1 09 Mar 2017 C1 H1 non-standard Yes Details →
1.4.0 29 Jan 2017 C1 H1 non-standard Yes Details →
1.3.3 24 Jan 2017 C1 H1 non-standard Yes Details →
1.3.2 14 Jan 2017 C1 H1 non-standard Yes Details →
1.3.1 03 Jan 2017 C1 H1 non-standard Yes Details →
1.3.0 02 Jan 2017 C1 H1 non-standard Yes Details →
1.2.1 01 Dec 2016 C1 H1 non-standard Yes Details →
1.2.0 23 Nov 2016 C1 H1 non-standard Yes Details →
1.1.0 03 Nov 2016 C1 H1 non-standard Yes Details →
1.0.9 26 Jul 2016 C1 H1 non-standard Yes Details →
1.0.8 21 Jul 2016 C1 H1 non-standard Yes Details →
1.0.7 10 Jul 2016 C1 H1 non-standard Yes Details →
1.0.6 24 Jun 2016 C1 H1 non-standard Yes Details →
1.0.5 24 Jun 2016 C1 H1 non-standard Yes Details →
1.0.4 23 Jun 2016 C1 H1 non-standard Yes Details →
1.0.3 16 Jun 2016 C1 H1 non-standard Yes Details →
1.0.2 16 Jun 2016 C1 H1 non-standard Yes Details →
1.0.1 16 Jun 2016 C1 H1 non-standard Yes Details →
1.0.0 14 Jun 2016 C1 H1 non-standard Yes Details →
0.13.5 31 May 2016 C1 H1 non-standard Yes Details →
0.13.4 07 Apr 2016 C1 H1 non-standard Yes Details →
0.13.3 24 Mar 2016 C1 H1 non-standard Yes Details →
0.13.2 09 Mar 2016 C1 H1 non-standard Yes Details →
0.13.1 21 Feb 2016 C1 H1 non-standard Yes Details →
0.13.0 18 Feb 2016 C1 H1 non-standard Yes Details →
0.12.1 09 Feb 2016 C1 H1 non-standard Yes Details →
0.12.0 27 Jan 2016 C1 H1 non-standard Yes Details →
0.11.0 15 Dec 2015 C1 H1 non-standard Yes Details →
0.10.1 03 Dec 2015 C1 H1 non-standard Yes Details →
0.10.0 26 Nov 2015 C1 H1 — Yes Details →
0.9.1 21 Oct 2015 C1 H1 — Yes Details →
0.8.4 28 Sep 2015 C1 H1 — Yes Details →
0.8.3 24 Sep 2015 C1 H1 — Yes Details →
0.8.2 18 Aug 2015 C1 H1 — Yes Details →
0.8.1 21 Jul 2015 C1 H1 — Yes Details →
0.8.0 21 Jul 2015 C1 H1 — Yes Details →
0.7.2 19 Jul 2015 C1 H1 — Yes Details →
0.7.1 19 Jul 2015 C1 H1 — Yes Details →
0.7.0 10 Jun 2015 C1 H1 — Yes Details →
0.6.4 30 May 2015 C1 H1 — Yes Details →
0.6.3 24 May 2015 C1 H1 — Yes Details →
0.6.2 24 May 2015 C1 H1 — Yes Details →
0.6.1 23 May 2015 C1 H1 — Yes Details →
0.6.0 23 May 2015 C1 H1 — Yes Details →
0.5.0 29 Apr 2015 C1 H1 — Yes Details →
0.4.2 20 Apr 2015 C1 H1 — Yes Details →
0.4.1 19 Apr 2015 C1 H1 — Yes Details →
0.4.0 12 Apr 2015 C1 H1 — Yes Details →
0.3.0 30 Mar 2015 C1 H1 — Yes Details →

The newest 120 of 153 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2023 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for jsreport

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 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

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About jsreport

Is jsreport safe to use?

Vulert records 2 vulnerabilities for jsreport in npm: 1 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is jsreport's Vulert package health score?

Vulert scores jsreport 71/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of jsreport affected?

No. 4.14.4, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does jsreport have?

2 vulnerabilities are recorded for jsreport in the npm ecosystem: 1 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new jsreport vulnerabilities disclosed?

0 vulnerabilities were recorded for jsreport in the last 12 months, and the oldest entry in this database dates to 13 Apr 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of jsreport are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.