Vulnerability Database · npm · @risingstack/protect · Version
@risingstack/protect 1.2.0
1.2.0 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 1.2.0.
Critical 0 High 0 Medium 1 Low 0 Unrated 0
-
Released 24 May 2017
Status latest release
Licence MIT
Also known from other sources 1
Newer releases 3
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
@risingstack/protect 1.2.0 vulnerabilities
1 vulnerability cover @risingstack/protect 1.2.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2018-1000160: Cross-Site Scripting in @risingstack/protect | 6.1 medium | No fix published | 25 Apr 2018 |
Looking for another version, or everything Vulert holds for @risingstack/protect?
Questions
About @risingstack/protect 1.2.0
Is @risingstack/protect 1.2.0 vulnerable?
Yes. 1 vulnerability in the Vulert database cover @risingstack/protect 1.2.0: 0 critical, 0 high, 1 medium and 0 low. The upgrade Vulert recommends is 1.2.0, and each entry above names the fixed version to move to.
Which version of @risingstack/protect should I use instead of 1.2.0?
1.2.0 is the version Vulert recommends for this release line, which is also the release the publisher currently ships. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 1.2.0 the latest release of @risingstack/protect?
Yes. 1.2.0 is the current release, published 24 May 2017. Staying on the current line is what keeps you inside the publisher's fixes.
How do I monitor @risingstack/protect for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @risingstack/protect version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.