# CVE-2012-0791: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML into Horde IMP and Groupware Webmail via various parameters, requiring user interaction to execute.

- **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:** Yes
- **Published:** 24 Jan 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DSA-2485-1, GHSA-2j7j-jvr9-h35r

## What is CVE-2012-0791?

CVE-2012-0791 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 Jan 2012. 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 Horde IMP before 5.0.18 and Horde Groupware Webmail Edition before 4.0.6 allow remote attackers to inject arbitrary web script or HTML via the (1) composeCache, (2) rtemode, or (3) filename_* parameters to the compose page; (4) formname parameter to the contacts popup window; or (5) IMAP mailbox names.  NOTE: some of these details are obtained from third party information.

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

## Which versions are affected by CVE-2012-0791?

It affects 3 products.


Products: Horde Dynamic Imp, Horde Groupware Webmail Edition, Horde Imp.

## How do I fix CVE-2012-0791?

Upgrade to a fixed version.

## Is CVE-2012-0791 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0791 and fix it if it is affected.

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

## Sources

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

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