{"api_version":"1","generated_at":"2026-04-26T02:38:59+00:00","cve":"CVE-2019-12923","urls":{"html":"https://cve.report/CVE-2019-12923","api":"https://cve.report/api/cve/CVE-2019-12923.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2019-12923","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2019-12923"},"summary":{"title":"CVE-2019-12923","description":"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.","state":"PUBLIC","assigner":"cve@mitre.org","published_at":"2019-07-08 21:15:00","updated_at":"2019-07-16 15:33:00"},"problem_types":["CWE-352"],"metrics":[],"references":[{"url":"http://www.mailenable.com/Premium-ReleaseNotes.txt","name":"http://www.mailenable.com/Premium-ReleaseNotes.txt","refsource":"CONFIRM","tags":["Release Notes","Vendor Advisory"],"title":"","mime":"text/plain","httpstatus":"200","archivestatus":"0"},{"url":"https://www.nccgroup.trust/uk/our-research/technical-advisory-multiple-vulnerabilities-in-mailenable/","name":"https://www.nccgroup.trust/uk/our-research/technical-advisory-multiple-vulnerabilities-in-mailenable/","refsource":"MISC","tags":["Release Notes","Third Party Advisory"],"title":"","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-12923","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-12923","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2019","cve_id":"12923","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"mailenable","cpe5":"mailenable","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"premium","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2019","cve_id":"12923","vulnerable":"1","versionEndIncluding":"1","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"mailenable","cpe5":"mailenable","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"premium","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"cve@mitre.org","ID":"CVE-2019-12923","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"n/a","version":{"version_data":[{"version_value":"n/a"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"refsource":"CONFIRM","name":"http://www.mailenable.com/Premium-ReleaseNotes.txt","url":"http://www.mailenable.com/Premium-ReleaseNotes.txt"},{"refsource":"MISC","name":"https://www.nccgroup.trust/uk/our-research/technical-advisory-multiple-vulnerabilities-in-mailenable/","url":"https://www.nccgroup.trust/uk/our-research/technical-advisory-multiple-vulnerabilities-in-mailenable/"}]}},"nvd":{"publishedDate":"2019-07-08 21:15:00","lastModifiedDate":"2019-07-16 15:33:00","problem_types":["CWE-352"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.0","vectorString":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"REQUIRED","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"HIGH","availabilityImpact":"NONE","baseScore":6.5,"baseSeverity":"MEDIUM"},"exploitabilityScore":2.8,"impactScore":3.6},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:M/Au:N/C:N/I:P/A:N","accessVector":"NETWORK","accessComplexity":"MEDIUM","authentication":"NONE","confidentialityImpact":"NONE","integrityImpact":"PARTIAL","availabilityImpact":"NONE","baseScore":4.3},"severity":"MEDIUM","exploitabilityScore":8.6,"impactScore":2.9,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":true}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:mailenable:mailenable:*:*:*:*:premium:*:*:*","versionStartIncluding":"6.0","versionEndExcluding":"6.90","cpe_name":[]},{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:mailenable:mailenable:*:*:*:*:premium:*:*:*","versionStartIncluding":"7.0","versionEndExcluding":"7.62","cpe_name":[]},{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:mailenable:mailenable:*:*:*:*:premium:*:*:*","versionStartIncluding":"8.00","versionEndExcluding":"8.64","cpe_name":[]},{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:mailenable:mailenable:*:*:*:*:premium:*:*:*","versionStartIncluding":"9.0","versionEndExcluding":"9.83","cpe_name":[]},{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:mailenable:mailenable:*:*:*:*:premium:*:*:*","versionStartIncluding":"10.00","versionEndExcluding":"10.24","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2019","CveId":"12923","Ordinal":"151273","Title":"CVE-2019-12923","CVE":"CVE-2019-12923","Year":"2019"},"notes":[{"CveYear":"2019","CveId":"12923","Ordinal":"1","NoteData":"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.","Type":"Description","Title":null},{"CveYear":"2019","CveId":"12923","Ordinal":"2","NoteData":"2019-07-08","Type":"Other","Title":"Published"},{"CveYear":"2019","CveId":"12923","Ordinal":"3","NoteData":"2019-07-08","Type":"Other","Title":"Modified"}]}}}