# CVE-2018-3755: Cross-Site Scripting in sexstatic

> Stored XSS in sexstatic allows attackers to inject HTML via directory names, potentially executing malicious scripts in user browsers.

- **Severity:** Medium 6.1 (`CVSS:3.1/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:** 1 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qfh2-6f7q-gr86

## What is CVE-2018-3755?

CVE-2018-3755 is a medium-severity cross-site scripting vulnerability in HackerOne sexstatic, published on 1 Jun 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

XSS in sexstatic <=0.6.2 causes HTML injection in directory name(s) leads to Stored XSS when malicious file is embed with <iframe> element used in directory name.

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

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

2 open source packages ship an affected version, including sexstatic. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sexstatic` | npm | All versions to 0.6.2 | None |
| `sexstatic` | npm | All versions to 0.6.2 | None |

Products: Sexstatic Project Sexstatic.

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

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

## Is CVE-2018-3755 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-3755 is a medium-severity cross-site scripting vulnerability in HackerOne sexstatic, published on 1 Jun 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-3755 in the wild and no public exploit code.

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

## Sources

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

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