CVE-2018-3755: XSS in sexstatic <=0.6.2 causes HTML injection in directory name(s) leads to Stored XSS when malicious file is
CVE-2018-3755 is a medium-severity flaw (CVSS 6.1) affecting sexstatic. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 6.1 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.9% (top 40%) |
| CISA exploited list | No |
| Weakness | CWE-79 |
| Published | 2018-06-01 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2018-3755?
sexstatic: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2018-3755 being exploited?
CVE-2018-3755 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2018-3755 affect?
CVE-2018-3755 affects sexstatic. Severity is medium (CVSS 6.1). 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.
How urgent is CVE-2018-3755?
Priority 41/100. Public exploit reference