CVE-2019-12925
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 · uneditedMailEnable Enterprise Premium 10.23 was vulnerable to multiple directory traversal issues, with which authenticated users could add, remove, or potentially read files in arbitrary folders accessible by the IIS user. This could lead to reading other users' credentials including those of SYSADMIN accounts, reading other users' emails, or adding emails or files to other users' accounts.
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 confidenceMailEnable Enterprise Premium 10.23 contains multiple directory traversal vulnerabilities that allow authenticated users to manipulate files in arbitrary folders accessible by the IIS service account. This enables reading sensitive data including user credentials and emails, as well as adding malicious files or emails to other user accounts.
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>= 6.0, < 6.90>= 7.0, < 7.62>= 8.00, < 8.64>= 9.0, < 9.83>= 10.00, < 10.24CVSS 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
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed MailEnable versionCheck the MailEnable version through the Windows Registry at HKLM\SOFTWARE\Mail Enable\Mail Enable\Version or inspect the MEWebMsg.dll file version in the bin directory if accessibleAffected if The version falls within these vulnerable ranges: 6.0 to 6.89, 7.0 to 7.61, 8.00 to 8.63, 9.0 to 9.82, or 10.00 to 10.23
-
Verify web mail interface is enabledConfirm that the MailEnable web mail component (MEWebMsg) is installed and the associated IIS application pool is running. Check IIS Manager for the MEWebMsg application or virtual directoryAffected if The web interface is exposed and accessible to authenticated users, which provides the attack vector for directory traversal
-
Confirm IIS service account has excessive file permissionsReview the IIS worker process identity permissions on the MailEnable mail storage directories (typically under the MailEnable\MAILROOT folder). Use icacls or file explorer to list permissions for the IIS app pool identityAffected if The IIS service account has write or modify permissions beyond the intended mail directories, enabling arbitrary file manipulation via traversal
-
Review for directory traversal attempts in logsExamine IIS and MailEnable web service logs for patterns containing ../ sequences or absolute path traversal in request parameters, particularly in web mail functionalityAffected if Logs show directory traversal patterns in requests from authenticated user sessions
A user is affected if they run a MailEnable version within the vulnerable ranges AND have the web mail interface enabled with the IIS service account having broad file system permissions.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data6.907.628.64
Apply the vendor patch or upgrade to a fixed version of MailEnable Enterprise Premium. Additionally, restrict IIS worker process permissions to the minimum required directories and implement strict access controls on mail storage paths.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12925 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-12925 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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