basicsecurity.net
Proof, not just disclosure.
Threats / MDaemon / CVE-2024-11182
CVE-2024-11182 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

MDaemon Email Server vulnerability

MDaemon Email Server contains a cross-site scripting vulnerability in HTML email handling that allows remote attackers to execute arbitrary JavaScript code.

Verdict

Today item — known-exploited.

A remote attacker can craft a malicious HTML email that executes arbitrary JavaScript in the context of a user's email client or webmail interface, potentially leading to session hijacking, credential theft, or malware distribution.

CISA KEV Yes · 2025-05-193EPSS 0.16346 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
8 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-05-19).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.16346 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: MDaemon, Email Server. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-79 Cross-site Scripting (XSS) — weakness family: Web / client.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft an HTML email containing malicious JavaScript code.
Business
Email infrastructure becomes a vector for client-side attacks against end users.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I send the email to target users through MDaemon, bypassing server-side validation.
Business
User trust in email communications is compromised as a delivery mechanism.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute JavaScript in the victim's browser when they open the email, stealing session tokens or credentials.
Business
User accounts and sensitive email data become accessible to attackers without additional authentication.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 8 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by ESET (CNA)
  • Named finder/reporter credit (CVE.org)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • Disclosure & credit2
    Catalogued by ESETCNA
    Credited with finding itMatthieu Faou (ESET)finder