# GHSA-g7mw-5cq6-fv82: Cross-Site Scripting in wangeditor

> Attackers can inject arbitrary JavaScript into links via the wangeditor library, leading to code execution in victim browsers.

- **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:** 2 Sep 2020

## What is GHSA-g7mw-5cq6-fv82?

GHSA-g7mw-5cq6-fv82 is a cross-site scripting vulnerability in wangeditor, published on 2 Sep 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 `wangeditor` are vulnerable to Cross-Site Scripting. The package fails to properly encode output, allowing arbitrary JavaScript to be inserted in links and executed by browsers.

## Recommendation

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

## Which versions are affected by GHSA-g7mw-5cq6-fv82?

2 open source packages ship an affected version, including wangeditor.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wangeditor` | npm | All versions | None |
| `wangeditor` | npm | All versions | None |

## How do I fix GHSA-g7mw-5cq6-fv82?

No fix has been published for GHSA-g7mw-5cq6-fv82 yet. Limit exposure of the affected software until one is available.

## Is GHSA-g7mw-5cq6-fv82 being exploited?

There is no known exploitation of GHSA-g7mw-5cq6-fv82 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-g7mw-5cq6-fv82 and fix it if it is affected.

What it is: GHSA-g7mw-5cq6-fv82 is a cross-site scripting vulnerability in wangeditor, published on 2 Sep 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-g7mw-5cq6-fv82 in the wild and no public exploit code.

Affected packages and fixed versions:
- wangeditor (npm): affected all versions; no fix listed
- wangeditor (npm): affected all versions; 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-g7mw-5cq6-fv82/ (Markdown: https://insights.sbomify.com/GHSA-g7mw-5cq6-fv82/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-g7mw-5cq6-fv82

---
From sbomify Insights: https://insights.sbomify.com/GHSA-g7mw-5cq6-fv82/
Summaries are generated and may contain mistakes; the official description above is the record.