# CVE-2022-41871: Command injection in SEPPmail

> An authenticated attacker can execute arbitrary code as root via command injection in the SEPPmail Admin Portal.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **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:** 28 Apr 2025
- **Updated:** 28 Apr 2025
- **Also known as:** GHSA-9mh9-7p8c-gr7g

## What is CVE-2022-41871?

CVE-2022-41871 is a medium-severity command injection vulnerability in SEPPmail, published on 28 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SEPPmail through 12.1.17 allows command injection within the Admin Portal. An authenticated attacker is able to execute arbitrary code in the context of the user root.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Seppmail Seppmail.

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

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

## Is CVE-2022-41871 being exploited?

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

## Other vulnerabilities in SEPPmail

- [CVE-2026-2743](https://insights.sbomify.com/CVE-2026-2743/): SEPPmail User Web Interface Arbitrary File Write to RCE (critical 10.0)
- [CVE-2026-27441](https://insights.sbomify.com/CVE-2026-27441/): PDF Password CMDi (critical 9.5)
- [CVE-2026-27442](https://insights.sbomify.com/CVE-2026-27442/): zip_attachments Path Traversal (critical 9.3)
- [CVE-2026-27443](https://insights.sbomify.com/CVE-2026-27443/): S/MIME Decryption Tag Sanitization Bypass (high 8.2)
- [CVE-2026-27444](https://insights.sbomify.com/CVE-2026-27444/): Header Email Address Parsing (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41871 and fix it if it is affected.

What it is: CVE-2022-41871 is a medium-severity command injection vulnerability in SEPPmail, published on 28 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-41871 in the wild and no public exploit code.

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

## Sources

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

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