# CVE-2025-30349: Cross-site scripting in IMP

> Attackers can execute arbitrary JavaScript via crafted HTML emails in Horde IMP, leading to account takeover.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Mar 2025
- **Updated:** 3 Apr 2025
- **Also known as:** DEBIAN-CVE-2025-30349, DLA-4113-1, GHSA-mchq-vv84-m9gr, UBUNTU-CVE-2025-30349

## What is CVE-2025-30349?

CVE-2025-30349 is a high-severity cross-site scripting vulnerability in Horde IMP, published on 21 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Horde IMP through 6.2.27, as used with Horde Application Framework through 5.2.23, allows XSS that leads to account takeover via a crafted text/html e-mail message with an onerror attribute (that may use base64-encoded JavaScript code), as exploited in the wild in March 2025.

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

## Which versions are affected by CVE-2025-30349?


## How do I fix CVE-2025-30349?

Apply the vendor's patch.

## Is CVE-2025-30349 being exploited?

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

Public exploit code:

- Horde IMP (through 6.2.27) vulnerability – obfuscation via HTML encoding – XSS payload (github_poc): https://github.com/natasaka/CVE-2025-30349

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-30349 and fix it if it is affected.

What it is: CVE-2025-30349 is a high-severity cross-site scripting vulnerability in Horde IMP, published on 21 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-30349 exists.

Affected product: Horde IMP. 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-2025-30349/ (Markdown: https://insights.sbomify.com/CVE-2025-30349/index.md)
```

## Sources

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

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