# CVE-2025-59332: 3DAlloy allows stored XSS through attributes provided to the 3d parser tag/function

> Attackers can inject arbitrary JavaScript via unsanitized attributes in the 3DAlloy MediaWiki extension, leading to stored XSS.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2025
- **Updated:** 15 Sep 2025
- **Also known as:** GHSA-f2rp-232x-mqrh

## What is CVE-2025-59332?

CVE-2025-59332 is a high-severity cross-site scripting vulnerability in dolfinus 3DAlloy, published on 15 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

3DAlloy is a lightWeight 3D-viewer for MediaWiki. From 1.0 through 1.8, the <3d> parser tag and the {{#3d}} parser function allow users to provide custom attributes that are then appended to the canvas HTML element that is being output by the extension. The attributes are not sanitized, which means that arbitrary JavaScript can be inserted and executed.

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

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


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

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

## Is CVE-2025-59332 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59332 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59332 is a high-severity cross-site scripting vulnerability in dolfinus 3DAlloy, published on 15 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59332 exists.

Affected product: dolfinus 3DAlloy. 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-59332/ (Markdown: https://insights.sbomify.com/CVE-2025-59332/index.md)
```

## Sources

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

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