dbcve.org
SeppmailApplication

CVE-2022-41871

HIGH · 8.8 CVSS v3.1 Published 2025-04-28
Fix available
A fix is available. Upgrade to after 12.1.17 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SEPPmail through version 12.1.17 contains a command injection vulnerability in its Admin Portal. An attacker with valid Admin Portal credentials can inject and execute arbitrary operating system commands with root-level privileges.

MitigationUpgrade to a patched version of SEPPmail (14.x or later recommended). If immediate patching is not feasible, restrict network access to the Admin Portal to trusted IP addresses only and enforce strong authentication credentials.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SeppmailApplication
Affected:<= 12.1.17

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SEPPmail installation and version
    Locate the SEPPmail installation and determine its version number. This may be visible in the product interface, a configuration file, or by querying the system directly. Compare the installed version against the affected range: any version <= 12.1.17 is vulnerable.
    Affected if The installed version is 12.1.17 or any earlier version.
  2. Verify Admin Portal is accessible
    Determine whether the SEPPmail Admin Portal interface is exposed and reachable on the network. This is typically accessible via HTTPS on a specific port (often 8443 or similar). Check if the Admin Portal login page loads from external or untrusted network locations.
    Affected if The Admin Portal is accessible from network segments that are not exclusively trusted.
  3. Confirm Admin Portal credentials
    Review the strength and exposure of Admin Portal credentials. Check if default credentials are still in use, if credentials have been changed from defaults, and whether credentials may have been compromised or shared broadly.
    Affected if Weak, default, or potentially compromised Admin Portal credentials are in use.
  4. Assess network exposure of Admin Portal
    Examine firewall rules, access control lists, or network segmentation to determine if the Admin Portal is reachable from untrusted networks or the internet. Identify any IP-based access restrictions that may be in place.
    Affected if The Admin Portal is reachable from untrusted IP addresses or networks without IP-based restrictions enabled.

A SEPPmail installation with Admin Portal accessible from untrusted networks, running version 12.1.17 or earlier, and using valid credentials is vulnerable to root-level command injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 12.1.17
Interim mitigation

Upgrade to a patched version of SEPPmail (14.x or later recommended). If immediate patching is not feasible, restrict network access to the Admin Portal to trusted IP addresses only and enforce strong authentication credentials.

Recommended fix Moderate confidence

SEPPmail version > 12.1.18 (contact Seppmail for the exact latest stable release)

  1. 1. Review the SEPPmail Admin Portal for any unauthorized changes or user accounts.
  2. 2. Check system logs for any signs of exploitation of CVE-2022-41871.
  3. 3. Plan an upgrade to a SEPPmail version newer than 12.1.17.
  4. 4. Before upgrading, create a complete backup of the SEPPmail configuration and data.
  5. 5. Review the official SEPPmail release notes for the target version to understand new features and any configuration changes.
  6. 6. Perform the upgrade in a test/staging environment first to validate compatibility.
  7. 7. After successful testing, apply the upgrade to production environment.
  8. 8. Verify the upgrade was successful and the Admin Portal is functioning correctly.
Caveat Review release notes for any configuration changes between 12.1.17 and the target version; test thoroughly in non-production first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Seppmail Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41871 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41871 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data