# CVE-2022-39258: mailcow-dockerized critical information misrepresentation can lead to phishing attacks through Swagger UI

> Attackers can spoof Swagger UI authorization links to redirect victims to phishing pages, stealing credentials or sensitive information.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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:** 27 Sep 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-vjgf-cp5p-wm45

## What is CVE-2022-39258?

CVE-2022-39258 is a high-severity vulnerability in mailcow-dockerized, published on 27 Sep 2022. 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 is a mailserver suite. A vulnerability innversions prior to 2022-09 allows an attacker to craft a custom Swagger API template to spoof Authorize links. This could redirect a victim to an attacker controller place to steal Swagger authorization credentials or create a phishing page to steal other information. The issue has been fixed with the 2022-09 mailcow Mootember Update. As a workaround, one may delete the Swapper API Documentation from their e-mail server.

Weakness: CWE-601 (URL Redirection to Untrusted Site), CWE-451 (User Interface (UI) Misrepresentation of Critical Information), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-39258?

It affects 1 product.


Products: Mailcow Mailcow\.

## How do I fix CVE-2022-39258?

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

## Is CVE-2022-39258 being exploited?

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

Public exploit code:

- Mailcow Dockerized Swagger UI - Cross-Site Scripting (nuclei): http/cves/2022/CVE-2022-39258.yaml

## 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-2022-39258 and fix it if it is affected.

What it is: CVE-2022-39258 is a high-severity vulnerability in mailcow-dockerized, published on 27 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39258 exists.

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

## Sources

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

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