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

> Remote attackers can inject arbitrary web script or HTML via specific parameters in SquirrelMail, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** Yes
- **Published:** 5 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-1241-1, GHSA-58cj-jwpm-3hvq, RHSA-2007:0022

## What is CVE-2006-6142?

CVE-2006-6142 is a medium-severity cross-site scripting vulnerability in Squirrelmail Squirrelmail, published on 5 Dec 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 SquirrelMail 1.4.0 through 1.4.9 allow remote attackers to inject arbitrary web script or HTML via the (1) mailto parameter in (a) webmail.php, the (2) session and (3) delete_draft parameters in (b) compose.php, and (4) unspecified vectors involving "a shortcoming in the magicHTML filter."

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `squirrelmail` | Red Hat:enterprise_linux:3::as | All versions | 0:1.4.8-4.el3 |
| `squirrelmail` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.4.8-4.el3 |
| `squirrelmail` | Red Hat:enterprise_linux:3::es | All versions | 0:1.4.8-4.el3 |
| `squirrelmail` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.4.8-4.el3 |
| `squirrelmail` | Red Hat:enterprise_linux:4::as | All versions | 0:1.4.8-4.el4 |
| `squirrelmail` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.4.8-4.el4 |
| `squirrelmail` | Red Hat:enterprise_linux:4::es | All versions | 0:1.4.8-4.el4 |
| `squirrelmail` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.4.8-4.el4 |

Products: Squirrelmail Squirrelmail.

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

Upgrade to a fixed version.

## Is CVE-2006-6142 being exploited?

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

## Other vulnerabilities in Squirrelmail Squirrelmail

- [CVE-2002-0516](https://insights.sbomify.com/CVE-2002-0516/): Command injection in n/a (critical 10.0)
- [CVE-2020-14932](https://insights.sbomify.com/CVE-2020-14932/): Deserialization in n/a (critical 9.8)
- [CVE-2020-14933](https://insights.sbomify.com/CVE-2020-14933/): Deserialization in n/a (high 8.8)
- [CVE-2017-7692](https://insights.sbomify.com/CVE-2017-7692/): Command injection in n/a (high 8.8)
- [CVE-2007-2631](https://insights.sbomify.com/CVE-2007-2631/): Cross-site request forgery in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6142 is a medium-severity cross-site scripting vulnerability in Squirrelmail Squirrelmail, published on 5 Dec 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-6142 in the wild and no public exploit code.

Affected product: Squirrelmail Squirrelmail. 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-6142/ (Markdown: https://insights.sbomify.com/CVE-2006-6142/index.md)
```

## Sources

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

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