CVE-2019-12923
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 · uneditedIn MailEnable Enterprise Premium 10.23, the potential cross-site request forgery (CSRF) protection mechanism was not implemented correctly and it was possible to bypass it by removing the anti-CSRF token parameter from the request. This could allow an attacker to manipulate a user into unwittingly performing actions within the application (such as sending email, adding contacts, or changing settings) on behalf of the attacker.
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 confidenceIn MailEnable Enterprise Premium 10.23, the CSRF protection mechanism can be bypassed by simply removing the anti-CSRF token parameter from HTTP requests. The application processes state-changing operations without properly validating that the token is present or required, allowing authenticated users to be tricked into performing unintended actions like sending emails, adding contacts, or modifying settings.
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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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.
-
Check MailEnable versionLocate the installed MailEnable version through the Windows Services panel, the web admin interface footer, or the MailEnable program directory. Compare the version number to the affected 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.Affected if The installed version falls within any of the affected version ranges listed.
-
Confirm web interface is accessibleDetermine if the MailEnable webmail or web admin interface is enabled and accessible by attempting to reach typical endpoints such as /mewebmail or /meadmin on the server, or by checking the IIS site configuration for MailEnable web services.Affected if The web interface is enabled and reachable.
-
Identify state-changing operationsReview the web interface functionality to identify operations that modify server state, such as composing and sending emails, adding contacts, or changing account settings.Affected if State-changing operations exist in the accessible web interface.
-
Verify CSRF token validation is absentCapture a legitimate HTTP request that performs a state-changing action and observe whether the application accepts the request when the anti-CSRF token parameter is removed or omitted entirely.Affected if The application processes the request successfully without the anti-CSRF token present.
You are affected if your MailEnable version falls within the listed affected ranges and the web interface is accessible and processes state-changing requests without requiring a valid anti-CSRF token.
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
Implement proper server-side CSRF token validation that rejects all state-changing requests lacking a valid anti-CSRF token, rather than merely processing requests without checking. Additionally, consider implementing SameSite cookie attributes and origin validation as defense-in-depth measures.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12923 — 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-12923 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