In 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.
References
| Link | Resource |
|---|---|
| http://www.mailenable.com/Premium-ReleaseNotes.txt | Release Notes Vendor Advisory |
| https://www.nccgroup.trust/uk/our-research/technical-advisory-multiple-vulnerabilities-in-mailenable/ | Release Notes Third Party Advisory |
| http://www.mailenable.com/Premium-ReleaseNotes.txt | Release Notes Vendor Advisory |
| https://www.nccgroup.trust/uk/our-research/technical-advisory-multiple-vulnerabilities-in-mailenable/ | Release Notes Third Party Advisory |
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 04:23
| Type | Values Removed | Values Added |
|---|---|---|
| References | () http://www.mailenable.com/Premium-ReleaseNotes.txt - Release Notes, Vendor Advisory | |
| References | () https://www.nccgroup.trust/uk/our-research/technical-advisory-multiple-vulnerabilities-in-mailenable/ - Release Notes, Third Party Advisory |
Information
Published : 2019-07-08 21:15
Updated : 2024-11-21 04:23
NVD link : CVE-2019-12923
Mitre link : CVE-2019-12923
CVE.ORG link : CVE-2019-12923
JSON object : View
Products Affected
mailenable
- mailenable
CWE
CWE-352
Cross-Site Request Forgery (CSRF)