# CVE-2008-5869: Cross-site scripting in n/a

> Authenticated attackers can inject arbitrary scripts via SNMP OID in Proxim Wireless Tsunami MP.11 devices, potentially compromising the management interface.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/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:** 8 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mm7x-c8mh-mw5q

## What is CVE-2008-5869?

CVE-2008-5869 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Jan 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cross-site scripting (XSS) vulnerability in the Proxim Wireless Tsunami MP.11 2411 with firmware 3.0.3 allows remote authenticated users to inject arbitrary web script or HTML via the system.sysName.0 SNMP OID.

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

## Which versions are affected by CVE-2008-5869?

It affects 1 product.


Products: Proxim Tsunami Mp.11 2411.

## How do I fix CVE-2008-5869?

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

## Is CVE-2008-5869 being exploited?

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

Public exploit code:

- Proxim Tsunami MP.11 2411 Wireless Access Point - 'system.sysName.0' SNMP HTML Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-5866](https://insights.sbomify.com/CVE-2008-5866/): Hardcoded credentials in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5869 and fix it if it is affected.

What it is: CVE-2008-5869 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Jan 2009. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5869 exists.

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

## Sources

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

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