dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 9 Jun 2025.
MdaemonApplication

CVE-2024-11182

MEDIUM · 6.1 CVSS v3.1 Published 2024-11-15
Fix available
A fix is available. Upgrade to 24.5.1 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An XSS issue was discovered in MDaemon Email Server before version 24.5.1c. An attacker can send an HTML e-mail message with JavaScript in an img tag. This could allow a remote attacker to load arbitrary JavaScript code in the context of a webmail user's browser window.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stored cross-site scripting (XSS) vulnerability in MDaemon Email Server's webmail interface allows remote attackers to inject arbitrary JavaScript via HTML email messages containing JavaScript in img tags. When webmail users view these malicious emails, the script executes in their browser context.

MitigationUpgrade MDaemon Email Server to version 24.5.1c or later to patch the vulnerability. Consider disabling HTML rendering in webmail as a temporary workaround until the upgrade is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MdaemonApplication
Affected:< 24.5.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check MDaemon version
    Open MDaemon GUI, go to Help > About, or check the version displayed in the main console window
    Affected if version is earlier than 24.5.1 (e.g., 24.0.0, 23.x, 22.x, etc.)
  2. Verify webmail is enabled
    In MDaemon GUI, navigate to Security > Security Settings > Webmail and confirm the Webmail service is turned on
    Affected if webmail is enabled and accessible to users
  3. Confirm HTML rendering is active in webmail
    In MDaemon GUI, go to Security > Security Settings > Webmail > Options, and check if 'Allow HTML in messages' or similar HTML rendering option is enabled
    Affected if HTML rendering is enabled, which allows the malicious img tag to execute JavaScript when users view crafted emails
  4. Identify webmail access method
    Check if users access webmail via /worldclient or /webmail paths on the server (e.g., https://mail.example.com/worldclient)
    Affected if webmail is publicly or internally accessible over HTTP/HTTPS

You are affected if MDaemon version is below 24.5.1 AND webmail with HTML rendering is enabled, allowing stored XSS via malicious img tags in emails to execute in users' browsers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 24.5.1 or later
Fixed in 24.5.1
Interim mitigation

Upgrade MDaemon Email Server to version 24.5.1c or later to patch the vulnerability. Consider disabling HTML rendering in webmail as a temporary workaround until the upgrade is applied.

Recommended fix High confidence

24.5.1c

  1. 1. Download MDaemon Email Server version 24.5.1c from the official MDaemon download page (files.mdaemon.com) or your trusted MDaemon distribution channel
  2. 2. Backup your current MDaemon configuration, data, and registry settings before proceeding
  3. 3. Stop the MDaemon service to ensure no active sessions during the upgrade
  4. 4. Run the installer for version 24.5.1c and follow the on-screen prompts to complete the upgrade
  5. 5. After installation completes, restart the MDaemon service
  6. 6. Verify the webmail interface is functioning correctly and the XSS vulnerability is resolved by testing with a benign HTML email containing an img tag with JavaScript
Caveat Review release notes for version 24.5.1c to check for any configuration or feature changes that may affect your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mdaemon Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11182 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-11182 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data