# CVE-2025-46824: Discourse Code Review Plugin vulnerable to XSS via auto link commits

> An attacker can execute arbitrary JavaScript in users' browsers by posting malicious GitHub commit links in the Discourse Code Review Plugin.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2025
- **Updated:** 20 Aug 2025
- **Also known as:** GHSA-358v-cwvc-gxh5

## What is CVE-2025-46824?

CVE-2025-46824 is a low-severity cross-site scripting vulnerability in discourse-code-review, published on 7 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Discourse Code Review Plugin allows users to review GitHub commits on Discourse. Prior to commit eed3a80, an attacker can execute arbitrary JavaScript on users' browsers by posting links to malicious GitHub commits. This problem is patched in commit eed3a80 of the discourse-code-review plugin. As a workaround, one may disable the plugin.

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

## Which versions are affected by CVE-2025-46824?


## How do I fix CVE-2025-46824?

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

## Is CVE-2025-46824 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-46824 and fix it if it is affected.

What it is: CVE-2025-46824 is a low-severity cross-site scripting vulnerability in discourse-code-review, published on 7 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-46824 in the wild and no public exploit code.

Affected product: discourse-code-review. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2025-46824/ (Markdown: https://insights.sbomify.com/CVE-2025-46824/index.md)
```

## Sources

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

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