dbcve.org
MailenableApplication

CVE-2026-44400

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-08
Fix available
A fix is available. Upgrade to 10.56 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
MailEnable Enterprise Premium 10.55 and earlier contains an improper authorization vulnerability in the WebAdmin mobile portal that allows attackers to bypass authentication checks by reusing AuthenticationToken cookies generated for low-privileged users. Attackers can obtain a token from the WebMail login endpoint using the PersistentLogin parameter and replay it against the WebAdmin portal to perform highly privileged administrative actions.

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

MailEnable Enterprise Premium 10.55 and earlier has an improper authorization vulnerability where AuthenticationToken cookies generated for low-privileged WebMail users can be replayed against the WebAdmin mobile portal to bypass authentication checks and perform highly privileged administrative actions.

MitigationImplement proper token scope validation in WebAdmin to ensure tokens are tied to their original authorization level, and reject tokens generated for lower-privilege interfaces.

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
MailenableApplication
Affected:< 10.56

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Check MailEnable version
    Open MailEnable Administrator, go to the About section, or check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Mail Enable\Mail Enable\Version
    Affected if The installed version is 10.55 or earlier (less than 10.56)
  2. Verify WebMail is enabled
    In MailEnable Administrator, expand Services > Protocols > HTTP and confirm the WebMail service is running and enabled
    Affected if WebMail is enabled and accessible to users
  3. Confirm WebAdmin mobile portal is accessible
    Attempt to access the WebAdmin mobile portal URL (typically /mewebmail/Mobile/) or check if port 8080 or 443 is listening for WebAdmin requests
    Affected if WebAdmin mobile portal is exposed and accepts authentication tokens
  4. Identify low-privilege WebMail accounts
    In MailEnable Administrator, review user accounts in the WebMail domain and note which accounts have Standard or Guest-level privileges rather than Administrator privileges
    Affected if Low-privilege WebMail users exist in the system
  5. Check for token scope validation
    Inspect WebAdmin configuration files (MEWebAdmin.config or similar in the WebAdmin directory) for AuthenticationToken validation settings, specifically looking for whether tokens are validated for scope or authorization level
    Affected if Token scope validation is not implemented or is misconfigured to allow cross-interface token replay

The environment is affected if MailEnable version is below 10.56 AND both WebMail and WebAdmin mobile portal are enabled, allowing a low-privilege user's AuthenticationToken to be replayed for admin actions.

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 10.56 or later
Fixed in 10.56
Interim mitigation

Implement proper token scope validation in WebAdmin to ensure tokens are tied to their original authorization level, and reject tokens generated for lower-privilege interfaces.

Recommended fix High confidence

MailEnable Enterprise Premium 10.56 or later

  1. 1. Verify current MailEnable installation version by checking the About section in WebAdmin or using the version information in the installation directory.
  2. 2. Download MailEnable Enterprise Premium version 10.56 or later from the official MailEnable website (www.mailenable.com).
  3. 3. Before upgrading, backup the MailEnable configuration, especially the AuthenticationToken settings and user accounts.
  4. 4. Apply the upgrade installation on the server, following the standard MailEnable upgrade procedure.
  5. 5. After upgrade, verify the WebAdmin mobile portal now properly validates authentication tokens across privilege levels.
  6. 6. Confirm that tokens generated for low-privileged users can no longer be reused to access privileged administrative functions in WebAdmin.
Caveat Standard upgrade within major version 10.x; review release notes for any configuration changes; test in non-production environment before deploying to production

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

Fix this in Mailenable Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44400 — 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-2026-44400 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