CVE-2019-12927
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 stored and reflected cross-site scripting (XSS) attacks. Because the session cookie did not use the HttpOnly flag, it was possible to hijack the session cookie by exploiting this vulnerability.
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 both stored and reflected XSS vulnerabilities. Additionally, session cookies lack the HttpOnly flag, allowing stolen session credentials to be accessed via client-side scripts when XSS is exploited.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 services panel, or look at the installation directory for a version file, or query the MEAdmin web interface for version informationAffected if The installed version falls within 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
-
Confirm web mail or web admin interface is accessibleAttempt to access the MailEnable web portal URLs (typically /mewebmail or /meadmin on the server) from a browserAffected if The web interface is exposed and reachable, as XSS requires user interaction with the web portal
-
Inspect session cookie for HttpOnly flagLog into the MailEnable web interface, open browser developer tools (F12), go to the Application or Cookies tab, and examine the session cookie for the HttpOnly attributeAffected if The session cookie lacks the HttpOnly flag, meaning it can be accessed via client-side scripts
-
Test for reflected XSS in web login pagesSubmit a test payload containing a benign script tag (such as <script>alert(1)</script>) into login or search fields and observe if the input is reflected back without encodingAffected if User input is reflected in the response without proper HTML encoding, enabling reflected XSS
-
Check for stored XSS in user-accessible fieldsExamine MailEnable web mail features (such as the address book, signature, or calendar fields) to see if submitted content is stored and displayed back to users without sanitizationAffected if User-supplied data is stored and rendered to other users without input validation or output encoding, enabling stored XSS
A user is affected if they run a MailEnable version within the specified ranges AND have the web interface exposed, with session cookies missing HttpOnly protection and input fields reflecting or storing unsanitized content.
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 input validation and output encoding to remediate XSS vectors; configure session cookies with the HttpOnly and Secure flags to prevent session hijacking.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12927 — 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-12927 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