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

> Remote attackers can inject arbitrary web script or HTML via email subjects, encoded URIs, or attachment filenames in Lotus Domino iNotes Client.

- **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:** 13 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hm25-jq8g-7p2m

## What is CVE-2006-0663?

CVE-2006-0663 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Feb 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

Multiple cross-site scripting (XSS) vulnerabilities in Lotus Domino iNotes Client 6.5.4 and 7.0 allow remote attackers to inject arbitrary web script or HTML via (1) an email subject; (2) an encoded javascript URI, as demonstrated using "java
script:"; or (3) when the Domino Web Access ActiveX control is not installed, via an email attachment filename.

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

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

It affects 1 product.


Products: Ibm Lotus Domino Inotes Client.

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

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

## Is CVE-2006-0663 being exploited?

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

Public exploit code:

- IBM Lotus Domino 6.x/7.0 - iNotes JavaScript: Filter Bypass (exploitdb)
- IBM Lotus Domino 6.x/7.0 iNotes - Email Subject Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-0662](https://insights.sbomify.com/CVE-2006-0662/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-0663 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Feb 2006. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0663 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-2006-0663/ (Markdown: https://insights.sbomify.com/CVE-2006-0663/index.md)
```

## Sources

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

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