CVE-2019-12926
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 did not use appropriate access control checks in a number of areas. As a result, it was possible to perform a number of actions, when logged in as a user, that that user should not have had permission to perform. It was also possible to gain access to areas within the application for which the accounts used were supposed to have insufficient access.
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 · moderate confidenceMailEnable Enterprise Premium 10.23 contains multiple Insecure Direct Object Reference (IDOR) vulnerabilities and broken access control flaws. Authenticated users can perform actions and access resources outside their intended permission boundaries by manipulating parameters or navigating to unauthorized areas within the application.
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
- High
CVSS:3.0/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 checksWork through these to decide whether this CVE applies to you.
-
Determine MailEnable versionCheck the installed MailEnable version via Windows Registry key (HKLM\SOFTWARE\MailEnable\InstallPath) or by inspecting the MailEnable administration console version informationAffected 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
-
Identify web admin interface exposureLocate the MailEnable web mail or web admin URL (commonly at /MEWebMail/ or /MEWebAdmin/ paths on the server's web server IIS configuration)Affected if The web interface is accessible and the version check above shows a vulnerable version
-
Enumerate user accounts and rolesAccess the MailEnable administration console, navigate to the user management section, and list all created user accounts with their assigned permission levels and group membershipsAffected if Multiple user accounts exist with varying permission levels, indicating the IDOR vulnerability could allow privilege escalation between these accounts
-
Test parameter manipulation exposureIf you have access to the web interface with a low-privilege account, attempt to access or modify parameters in URLs or form submissions that reference other user IDs, mailboxes, or administrative resources (for example, manipulating mailbox ID or user ID parameters in web requests)Affected if Requests succeed in accessing or modifying data belonging to other users or higher-privilege accounts by simply changing parameter values
You are affected if your installed MailEnable version is within any of the vulnerable ranges listed and the web interface is accessible to authenticated users who could exploit the IDOR and broken access control flaws.
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
Update to a patched version of MailEnable Enterprise Premium. Review user role configurations and implement proper authorization checks on all sensitive operations.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12926 — 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-12926 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