# CVE-2026-38472: Cross-site scripting in n/a

> Remote attackers can inject arbitrary JavaScript via forum reward comments, leading to potential session hijacking or malicious actions.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 25 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-723j-f577-m6gp

## What is CVE-2026-38472?

CVE-2026-38472 is a medium-severity cross-site scripting vulnerability in n/a, published on 25 Aug 2026. 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

A Stored XSS vulnerability in forum reward comments in GazellePW (GazellePosterWall) commit 86c4bedf727691b5a97af42a4864869d18446449 allows remote attackers to inject arbitrary JavaScript via the c parameter in /forums.php?action=ajax_get_jf which is later rendered in the data-tooltip attribute in /forums.php?action=viewthread and interpreted as HTML by the Tooltipster configuration.

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

## Which versions are affected by CVE-2026-38472?


## How do I fix CVE-2026-38472?

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

## Is CVE-2026-38472 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-38472 and fix it if it is affected.

What it is: CVE-2026-38472 is a medium-severity cross-site scripting vulnerability in n/a, published on 25 Aug 2026. 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 CVE-2026-38472 in the wild and no public exploit code.

Affected product: n/a. 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-2026-38472/ (Markdown: https://insights.sbomify.com/CVE-2026-38472/index.md)
```

## Sources

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

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