mailcow: dockerized vulnerable to Second Order SQL Injection in quarantine category via API
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| mailcow | mailcow-dockerized | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mailcow | Mailcow Dockerized |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 8.6% (8.565% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mailcow
Mailcow mailcow Dockerized |
|
| Vendors & Products |
Mailcow
Mailcow mailcow Dockerized |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | mailcow: dockerized is an open source groupware/email suite based on docker. Versions prior to 2026-03b have a second-order SQL injection vulnerability in the quarantine_category field via the Mailcow API. The /api/v1/add/mailbox endpoint stores quarantine_category without validation or sanitization. This value is later used by quarantine_notify.py, which constructs SQL queries using unsafe % string formatting instead of parameterized queries. This results in a delayed (second-order) SQL injection when the quarantine notification job executes, allowing an attacker to inject arbitrary SQL. Using a UNION SELECT, sensitive data (e.g., admin credentials) can be exfiltrated and rendered inside quarantine notification emails. Version 2026-03b fixes the vulnerability. | |
| Title | mailcow: dockerized vulnerable to Second Order SQL Injection in quarantine category via API | |
| Weaknesses | CWE-116 CWE-20 CWE-564 CWE-89 |
|
| References |
| |
| Metrics |
cvssV3_1
|