# CVE-2025-25198: mailcow: dockerized vulnerable to password reset poisoning

> Attackers can poison password reset links via Host header manipulation, leading to account takeover if users click the malicious link.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Feb 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-3mvx-qw4r-fcqf

## What is CVE-2025-25198?

CVE-2025-25198 is a high-severity vulnerability in mailcow-dockerized, published on 12 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

mailcow: dockerized is an open source groupware/email suite based on docker. Prior to version 2025-01a, a vulnerability in mailcow's password reset functionality allows an attacker to manipulate the `Host HTTP` header to generate a password reset link pointing to an attacker-controlled domain. This can lead to account takeover if a user clicks the poisoned link. Version 2025-01a contains a patch. As a workaround, deactivate the password reset functionality by clearing `Notification email sender` and `Notification email subject` under System -> Configuration -> Options -> Password Settings.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

It affects 1 product.


Products: Mailcow Mailcow\.

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

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

## Is CVE-2025-25198 being exploited?

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

Public exploit code:

- PoC for CVE-2025-25198: automated Host header poisoning test for Mailcow - HTTPS listener, automatic cookie/CSRF handling, captures first reset link. (github_poc): https://github.com/Groppoxx/CVE-2025-25198-PoC
- Captures password reset tokens from Mailcow Host header injection attacks.  (github_poc): https://github.com/enzocipher/CVE-2025-25198
- mailcow 2025-01a - Host Header Password Reset Poisoning (exploitdb)

## Other vulnerabilities in mailcow-dockerized

- [CVE-2025-53909](https://insights.sbomify.com/CVE-2025-53909/): mailcow: dockerized vulnerable to SSTI in Quota and Quarantine Notification Template (critical 9.1)
- [CVE-2024-24760](https://insights.sbomify.com/CVE-2024-24760/): Mailcow Docker Container Exposure to Local Network (high 8.8)
- [CVE-2023-34108](https://insights.sbomify.com/CVE-2023-34108/): Manipulation of Internal Dovecot Variables in mailcow via crafted Passwords (high 8.8)
- [CVE-2022-31138](https://insights.sbomify.com/CVE-2022-31138/): OS Command Injection in mailcow (high 8.8)
- [CVE-2022-31245](https://insights.sbomify.com/CVE-2022-31245/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25198 is a high-severity vulnerability in mailcow-dockerized, published on 12 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-25198 in the wild and no public exploit code.

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

## Sources

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

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