# CVE-2026-58451: Horde IMP < 7.0.1 Path Traversal via Compose.php img src

> Authenticated attackers can read arbitrary server files via path traversal in Horde IMP, potentially exfiltrating sensitive data through email.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-58451, GHSA-mv7w-qwqh-w2g9, UBUNTU-CVE-2026-58451

## What is CVE-2026-58451?

CVE-2026-58451 is a high-severity path traversal vulnerability in horde imp, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Horde IMP before 7.0.1 contains a path traversal vulnerability in lib/Compose.php that allows authenticated attackers to read arbitrary files from the server filesystem by embedding traversal sequences after a CKEditor path prefix in img src URLs. Attackers can bypass the stripos() prefix validation by appending sequences such as traversal segments after the matching prefix, causing file_get_contents() to read sensitive files whose contents are then exfiltrated as MIME parts in outgoing email; unauthenticated exploitation is also achievable via CSRF against an active authenticated session.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-58451?


## How do I fix CVE-2026-58451?

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

## Is CVE-2026-58451 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-58451 and fix it if it is affected.

What it is: CVE-2026-58451 is a high-severity path traversal vulnerability in horde imp, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-58451 in the wild and no public exploit code.

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-2026-58451/ (Markdown: https://insights.sbomify.com/CVE-2026-58451/index.md)
```

## Sources

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

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