# CVE-2005-3425: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML into GNUMP3D, potentially compromising user sessions or data.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/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:** Yes
- **Published:** 1 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j986-v7h3-7q9r

## What is CVE-2005-3425?

CVE-2005-3425 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Nov 2005. 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

Cross-site scripting (XSS) vulnerability in GNUMP3D before 2.9.6 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors, a different vulnerability than CVE-2005-3424.

## Which versions are affected by CVE-2005-3425?

It affects 1 product.


Products: Gnu Gnump3d.

## How do I fix CVE-2005-3425?

Upgrade to a fixed version.

## Is CVE-2005-3425 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-3697](https://insights.sbomify.com/CVE-2019-3697/): Local privilege escalation from user gnump3d to root (high 7.7)
- [CVE-2005-3355](https://insights.sbomify.com/CVE-2005-3355/): Path traversal in n/a (medium 6.4)
- [CVE-2007-6130](https://insights.sbomify.com/CVE-2007-6130/): Missing authorization in n/a (medium 5.0)
- [CVE-2005-3123](https://insights.sbomify.com/CVE-2005-3123/): Path traversal in n/a (medium 5.0)
- [CVE-2005-3424](https://insights.sbomify.com/CVE-2005-3424/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3425 and fix it if it is affected.

What it is: CVE-2005-3425 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Nov 2005. 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-2005-3425 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-2005-3425/ (Markdown: https://insights.sbomify.com/CVE-2005-3425/index.md)
```

## Sources

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

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