# CVE-2018-16474: Stored Cross-Site Scripting in tianma-static

> An attacker can execute arbitrary JavaScript via stored XSS in the tianma-static npm module, potentially compromising user sessions.

- **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:** 6 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jhgp-hvj6-x2p2

## What is CVE-2018-16474?

CVE-2018-16474 is a medium-severity cross-site scripting vulnerability in npm tianma-static, published on 6 Nov 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

A stored xss in tianma-static module versions <=1.0.4 allows an attacker to execute arbitrary javascript.

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

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

2 open source packages ship an affected version, including tianma-static. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tianma-static` | npm | All versions to 1.0.4 | None |
| `tianma-static` | npm | All versions to 1.0.4 | None |

Products: Tianma-Static Project Tianma-Static.

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

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

## Is CVE-2018-16474 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-16474 is a medium-severity cross-site scripting vulnerability in npm tianma-static, published on 6 Nov 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-16474 in the wild and no public exploit code.

Affected packages and fixed versions:
- tianma-static (npm): affected all versions up to 1.0.4; no fix listed
- tianma-static (npm): affected all versions up to 1.0.4; 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-16474/ (Markdown: https://insights.sbomify.com/CVE-2018-16474/index.md)
```

## Sources

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

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