# CVE-2018-1000160: Cross-Site Scripting in @risingstack/protect

> The protect library incorrectly validates certain XSS strings as safe, allowing attackers to bypass XSS protections in applications using this library.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vpch-rxw3-fgx8

## What is CVE-2018-1000160?

CVE-2018-1000160 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

RisingStack protect version 1.2.0 and earlier contains a Cross Site Scripting (XSS) vulnerability in isXss() function in lib/rules/xss.js that can result in dangerous XSS strings being validated as safe. This attack appears to be exploitable via A number of XSS strings(26) detailed in the GitHub issue #16.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2018-1000160?

2 open source packages ship an affected version, including @risingstack/protect. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@risingstack/protect` | npm | All versions to 1.2.0 | None |
| `@risingstack/protect` | npm | All versions to 1.2.0 | None |

Products: Risingstack Protect.

## How do I fix CVE-2018-1000160?

No fix has been published for CVE-2018-1000160 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-1000160 being exploited?

There is no known exploitation of CVE-2018-1000160 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1000160 and fix it if it is affected.

What it is: CVE-2018-1000160 is a medium-severity cross-site scripting vulnerability in n/a, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-1000160 in the wild and no public exploit code.

Affected packages and fixed versions:
- @risingstack/protect (npm): affected all versions up to 1.2.0; no fix listed
- @risingstack/protect (npm): affected all versions up to 1.2.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1000160/ (Markdown: https://insights.sbomify.com/CVE-2018-1000160/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1000160
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1000160
- OSV: https://osv.dev/vulnerability/CVE-2018-1000160

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1000160/
Summaries are generated and may contain mistakes; the official description above is the record.