CVE-2006-6291 json
Stack overflow in the IMAP module (MEIMAPS.EXE) in MailEnable Professional 1.6 through 1.83 and 2.0 through 2.33, and MailEnable Enterprise…
published 2006-12-05 19 y ago modified 2026-06-16 4 mo ago also EUVD-2006-6274
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.2%
- EPSS 3.2% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
Stack overflow in the IMAP module (MEIMAPS.EXE) in MailEnable Professional 1.6 through 1.83 and 2.0 through 2.33, and MailEnable Enterprise 1.1 through 1.40 and 2.0 through 2.33, allows remote authenticated users to cause a denial of service (crash) via a long argument containing * (asterisk) and ? (question mark) characters to the DELETE command, as addressed by the ME-10020 hotfix.
Patch / fix
- mailenable.com/hotfix/ patch
- secunia.com/advisories/23080 advisory
Exploit prediction
3.22% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:L/Au:S/C:N/I:N/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
secunia.com
/advisories/23080
third-party-advisory, patch, vendor-advisory
-
mailenable.com
/hotfix/
patch
-
vupen.com
/english/advisories/2006/4778
vdb-entry, vendor-advisory
-
secunia.com
/secunia_research/2006-71/advisory/
vendor-advisory
-
securitytracker.com
/id?1017276
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/21362
vdb-entry, third-party-advisory
-
securitytracker.com
/id?1017319
vdb-entry, third-party-advisory
-
securityfocus.com
/archive/1/453118/100/100/threaded
mailing-list, third-party-advisory, vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/30614
vdb-entry
Sources
- CVE List CVE-2006-6291
- NVD CVE-2006-6291
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.