dbcve.org
MailenableApplication

CVE-2015-9280

CRITICAL · 10.0 CVSS v3.1 Published 2019-01-16
Fix available
A fix is available. Upgrade to 8.60 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
MailEnable before 8.60 allows XXE via an XML document in the request.aspx Options parameter.

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 confidence

MailEnable before version 8.60 contains an XML External Entity (XXE) injection vulnerability in the request.aspx web page. The Options parameter accepts XML documents that are parsed without proper entity restriction, allowing attackers to read internal files, perform server-side request forgery, or denial of service.

MitigationUpgrade MailEnable to version 8.60 or later to patch the vulnerability. If immediate upgrade is not possible, disable XML processing in the request.aspx handler or implement XML input validation/filtering at the web application firewall level.

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
MailenableApplication
Affected:< 8.60

CVSS 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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify MailEnable installation
    Check for MailEnable installation on the system - look for the MailEnable installation directory (typically C:\Program Files\MailEnable or C:\Program Files (x86)\MailEnable) or verify the MailEnable service is running via Services.msc
    Affected if MailEnable is installed and running
  2. Determine installed MailEnable version
    Locate the MailEnable version information - typically found in the MailEnable Administrator console under Server status, or check the version.dll or readme.txt in the installation directory, or examine the assembly version of MailEnable.Core.dll in the bin folder
    Affected if The installed version is lower than 8.60 (e.g., 8.53, 8.54, 8.55, etc.)
  3. Confirm request.aspx is exposed
    Check if the request.aspx web page exists and is accessible - typically found in the MailEnable web mail or web admin directories (e.g., /MEWebMail/request.aspx or /webadmin/request.aspx). Attempt to access this endpoint via HTTP/HTTPS to verify it responds.
    Affected if The request.aspx page is accessible and responds to requests
  4. Verify XML processing is enabled
    Check the web.config or application configuration for the request.aspx handler to confirm XML parsing is enabled for the Options parameter. This may involve examining the System.Xml.XmlDocument or similar XML processing configuration in the MailEnable web application configuration files.
    Affected if XML processing is enabled and the Options parameter accepts XML input without XXE protection

A system is affected if it runs MailEnable with version lower than 8.60 AND has the request.aspx endpoint accessible with XML processing enabled for the Options parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.60 or later
Fixed in 8.60
Interim mitigation

Upgrade MailEnable to version 8.60 or later to patch the vulnerability. If immediate upgrade is not possible, disable XML processing in the request.aspx handler or implement XML input validation/filtering at the web application firewall level.

Recommended fix High confidence

MailEnable 8.60 or later

  1. 1. Back up the current MailEnable configuration and all mail data before proceeding
  2. 2. Download MailEnable version 8.60 or later from the official MailEnable website or trusted vendor distribution channel
  3. 3. Execute the installer and follow the vendor's documented upgrade procedure for your current version
  4. 4. After upgrade completion, verify the MailEnable services are running correctly
  5. 5. Test the webmail/request.aspx functionality to confirm normal operation
  6. 6. Validate that the XXE vulnerability is remediated by reviewing that XML parsing in request.aspx no longer processes external entities
Caveat Standard upgrade risk applies - test in non-production environment first; ensure compatibility with existing integrations and configurations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mailenable Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-9280 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-9280 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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