CVE-2025-40631
Icewarp Mail Server 11.4.0
Raw vector
CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-40631 is a low-severity Improper Neutralization of HTTP Headers for Scripting Syntax (CWE-644) vulnerability in Icewarp Mail Server. Its CVSS base score is 2.0 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-15437
- 🇪🇸 INCIBE: www.incibe.es
Vulnerability Data
HTTP host header injection vulnerability in Icewarp Mail Server affecting version 11.4.0. By modifying the Host header and adding a payload, arbitrary JavaScript code can be executed on page load. The user must interact with a malicious link to be…
more
redirected.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V4.2.3
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly requires checking/neutralizing untrusted data such as HTTP headers before they reach browser components.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require proper output encoding and header sanitization to prevent scripting injection.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing catches header-injection issues before release, covering most of the weakness.
Secure development lifecycle mandates input validation and output encoding that directly prevents header-injection flaws.
Application security requirements explicitly call for neutralizing untrusted data in HTTP headers.
Secure architecture principles reduce injection surfaces but do not prescribe header-specific controls.
Secure coding standards require proper escaping or rejection of scripting syntax in HTTP headers.