CVE-2019-12923

N/A
Published: July 8, 2019 at 08:58 PM UTC
Updated: June 17, 2026 at 02:15 AM UTC
1 product affected across 1 vendorMailenable

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.6%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

10.00 ≤ v < 10.246.0 ≤ v < 6.907.0 ≤ v < 7.628.00 ≤ v < 8.649.0 ≤ v < 9.83
Affected range stops below 10.24, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.90, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.62, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.64, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.83, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (2)

CVSS

Confidentiality
NONE
Integrity
PARTIAL
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-352

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card