# CVE-2006-0091: Cross-site scripting in n/a

> Remote attackers can inject arbitrary scripts via email attachments in Open-Xchange webmail when Inline HTML is enabled, requiring user interaction to view the email.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jmmv-wmgj-w2qx

## What is CVE-2006-0091?

CVE-2006-0091 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 Jan 2006. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in webmail in Open-Xchange 0.8.1-6 and earlier, with "Inline HTML" enabled, allows remote attackers to inject arbitrary web script or HTML via e-mail attachments, which are rendered inline.

## Which versions are affected by CVE-2006-0091?

It affects 1 product.


Products: Open-Xchange Open-Xchange.

## How do I fix CVE-2006-0091?

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

## Is CVE-2006-0091 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2738](https://insights.sbomify.com/CVE-2006-2738/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0091 and fix it if it is affected.

What it is: CVE-2006-0091 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 Jan 2006. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-0091 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-2006-0091/ (Markdown: https://insights.sbomify.com/CVE-2006-0091/index.md)
```

## Sources

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

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