CVE-2024-11182
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.
do firstUpgrade to a fixed release: 24.5.1.
Can a WAF block it? No. The malicious input is delivered via an HTML email message, which is not an HTTP request but email protocol traffic. The attack involves JavaScript in an img tag inside the email body, which looks like normal email content and cannot be reliably distinguished by a web application firewall.
Also consider: CSP · output encoding
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-11182 being exploited?
Yes. CVE-2024-11182 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-11182?
CVE-2024-11182 is rated Medium with a CVSS score of 6.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-11182?
Yes. A fix has been recorded for CVE-2024-11182. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-11182 affect?
CVE-2024-11182 affects mdaemon:mdaemon. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected<= 24.5.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 21 May 2025 (SSVC 2.0.3).
timeline
- 15 Nov 2024Published
- 19 May 2025Added to CISA KEV (exploited in the wild) · 185 days (about 6 months) later
- 21 May 2025CISA SSVC assessment: exploitation active · 2 days later
- 9 Jun 2025CISA remediation due date (US federal agencies) · 19 days later
- 21 Oct 2025CVE record last updated · 135 days (about 5 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Linkfiles.mdaemon.com /mdaemon/beta/RelNotes_en.html
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-11182
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.