# GHSA-5p28-63mc-cgr9: Cross-Site Scripting bypass in html-purify

> An XSS vulnerability in html-purify allows attackers to execute JavaScript via unsanitized object tag data attributes, requiring user interaction.

- **Severity:** Not scored
- **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:** 4 Dec 2020

## What is GHSA-5p28-63mc-cgr9?

GHSA-5p28-63mc-cgr9 is a cross-site scripting vulnerability in html-purify, published on 4 Dec 2020. 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

All versions of html-purify are vulnerable to cross-site scripting. The data attribute inside of object tags is not properly sanitized and allows javascript URIs leading to code execution.

No fix is currently available. Consider using an alternative package until a fix is made available.

## Which versions are affected by GHSA-5p28-63mc-cgr9?

2 open source packages ship an affected version, including html-purify.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `html-purify` | npm | All versions to 1.1.0 | None |
| `html-purify` | npm | All versions to 1.1.0 | None |

## How do I fix GHSA-5p28-63mc-cgr9?

No fix has been published for GHSA-5p28-63mc-cgr9 yet. Limit exposure of the affected software until one is available.

## Is GHSA-5p28-63mc-cgr9 being exploited?

There is no known exploitation of GHSA-5p28-63mc-cgr9 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-5p28-63mc-cgr9 and fix it if it is affected.

What it is: GHSA-5p28-63mc-cgr9 is a cross-site scripting vulnerability in html-purify, published on 4 Dec 2020. 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 GHSA-5p28-63mc-cgr9 in the wild and no public exploit code.

Affected packages and fixed versions:
- html-purify (npm): affected all versions up to 1.1.0; no fix listed
- html-purify (npm): affected all versions up to 1.1.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/GHSA-5p28-63mc-cgr9/ (Markdown: https://insights.sbomify.com/GHSA-5p28-63mc-cgr9/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-5p28-63mc-cgr9

---
From sbomify Insights: https://insights.sbomify.com/GHSA-5p28-63mc-cgr9/
Summaries are generated and may contain mistakes; the official description above is the record.