CVE-2019-12924
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 XML External Entity Injection (XXE) attacks that could be exploited by an unauthenticated user. It was possible for an attacker to use a vulnerability in the configuration of the XML processor to read any file on the host system. Because all credentials were stored in a cleartext file, it was possible to steal all users' credentials (including the highest privileged users).
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 an XML External Entity Injection (XXE) vulnerability in its XML processor configuration. An unauthenticated attacker can exploit this by sending specially crafted XML requests to read arbitrary files from the host system. The critical impact stems from MailEnable storing all user credentials in cleartext files, allowing attackers to steal all credentials including those of highest-privileged users.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm MailEnable installationCheck for MailEnable in installed programs list (Windows Control Panel > Programs and Features) or look for MailEnable directories in the file system, typically under C:\Program Files\MailEnable or C:\MailEnableAffected if MailEnable Enterprise Premium is installed on the system
-
Determine installed MailEnable versionOpen MailEnable Administrator, go to the About section, or check the version in the MailEnable installation directory (often in a README or version info file)Affected if The installed version falls within any of these ranges: 6.0 to <6.90, 7.0 to <7.62, 8.00 to <8.64, 9.0 to <9.83, or 10.00 to <10.24
-
Verify XML processor endpoint is accessibleIdentify if the MailEnable web interface or API endpoint that processes XML requests is exposed externally. Check IIS or the web server configuration for MailEnable virtual directories or endpoints that handle XML inputAffected if The XML processing endpoint is reachable from the network without authentication
-
Check for cleartext credential storageLocate the MailEnable data directory and examine the directory where user credentials are stored. Look for files containing usernames and passwords in plaintext formatAffected if Credentials are stored in cleartext files within the MailEnable data directory (the critical impact of this vulnerability)
-
Review web server logs for XXE indicatorsExamine IIS or MailEnable web logs for suspicious XML requests containing DOCTYPE, ENTITY, or SYSTEM keywords, or requests attempting to access file:// URLsAffected if Log analysis reveals malformed XML requests with external entity references or anomalous file access attempts
A user is affected if MailEnable Enterprise Premium is installed with a version within the affected ranges AND the XML processing endpoint is network-accessible, exposing cleartext credential files to potential unauthenticated read access.
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.
dbcve · scoped6.907.628.64
Upgrade to a patched version of MailEnable Enterprise that addresses the XXE vulnerability. Additionally, configure the XML parser to disable external entity processing as a hardening measure.
Minimum fixed versions: 6.90, 7.62, 8.64, or 9.83 (or later releases within each major version branch)
- 1. Identify the currently installed MailEnable version by checking the application or Windows Programs list
- 2. Based on the installed version, upgrade to the minimum fixed version: for 6.x upgrade to 6.90 or later; for 7.x upgrade to 7.62 or later; for 8.x upgrade to 8.64 or later; for 9.x upgrade to 9.83 or later
- 3. Download the appropriate MailEnable update or installer from the official MailEnable website (www.mailenable.com)
- 4. Back up the MailEnable configuration and data directories before applying the upgrade
- 5. Stop the MailEnable services before upgrading
- 6. Apply the upgrade following MailEnable's standard upgrade procedure
- 7. After upgrade, verify the XML parser configuration has been hardened to prevent XXE attacks
- 8. Restart MailEnable services and verify the webmail and administrative interfaces are functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- 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-12924 — 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-12924 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