Vulnerability Database · npm · valine · Version
valine 1.2.0-beta1
1.2.0-beta1 is affected by 4 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 1.5.3.
Critical 1 High 0 Medium 3 Low 0 Unrated 0
-
Released 07 Jul 2018
Licence GPL-2.0
Also known from other sources 4
Newer releases 92
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
valine 1.2.0-beta1 vulnerabilities
4 vulnerabilities cover valine 1.2.0-beta1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2022-38545: Valine Code Injection Vulnerability | 9.6 critical | 1.5.0 | 20 Sep 2022 |
| CVE-2018-19289: Valine - HTML Injection Vulnerability | 6.1 medium | 1.3.4 | 21 Nov 2018 |
| CVE-2020-28847: Cross Site Scripting in valine | 5.4 medium | 1.4.15 | 06 Apr 2022 |
| CVE-2021-34801: Denial of Service in Valine | 5.3 medium | No fix published | 21 Jun 2021 |
Looking for another version, or everything Vulert holds for valine?
Questions
About valine 1.2.0-beta1
Is valine 1.2.0-beta1 vulnerable?
Yes. 4 vulnerabilities in the Vulert database cover valine 1.2.0-beta1: 1 critical, 0 high, 3 medium and 0 low. The upgrade Vulert recommends is 1.5.3, and each entry above names the fixed version to move to.
Which version of valine should I use instead of 1.2.0-beta1?
1.5.3 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 1.2.0-beta1 the latest release of valine?
No. 1.2.0-beta1 was published 07 Jul 2018, 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 valine for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the valine version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.