CVE-2022-29975
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 · uneditedAn Authenticated Reflected Cross-site scripting at CC Parameter was discovered in MDaemon before 22.0.0 .
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 · moderate confidenceAuthenticated reflected cross-site scripting (XSS) vulnerability in MDaemon email server before version 22.0.0. The CC parameter in the web interface does not properly sanitize user input, allowing an authenticated attacker to inject malicious JavaScript that gets reflected back in the HTTP response.
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< 22.0.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm MDaemon is installedCheck for the MDaemon service in Windows Services (services.msc) or look for the installation directory typically at C:\MDaemon or C:\Program Files\MDaemonAffected if MDaemon service or installation directory exists on the system
-
Determine installed MDaemon versionOpen MDaemon's About dialog from the system tray icon, or check the version.txt file in the MDaemon installation directory, or run: reg query 'HKLM\SOFTWARE\Alt-N Technologies\MDaemon' /v VersionAffected if The displayed version number is lower than 22.0.0 (for example, 21.x.x or earlier)
-
Check if WebMail or WorldClient is enabledOpen MDaemon GUI, go to Setup > Web Services / WebMail, or inspect the MDaemon.ini configuration file for entries under [WebMail] or [WorldClient] sectionsAffected if WebMail or WorldClient web interface is enabled and accessible over HTTP/HTTPS
-
Verify the CC parameter is in useThe vulnerability affects the CC parameter in the webmail interface. Check if the webmail component accepts email input with CC fields. This is typically available when composing emails through the web interface at /WorldClient or /WebMail endpointsAffected if The web interface is active and users can compose emails with CC fields through the browser
You are affected if MDaemon version is below 22.0.0 AND the WorldClient/WebMail web interface is enabled and accessible, allowing authenticated users to compose emails with CC fields.
Generated from the published advisory. Verify against your own configuration.
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 · scoped22.0.0
Upgrade to MDaemon version 22.0.0 or later which contains the security patch for this vulnerability.
MDaemon 22.0.0 or later
- Download MDaemon version 22.0.0 or later from the official MDaemon website or your licensed download location
- Backup your current MDaemon configuration and data
- Stop the MDaemon service before upgrading
- Install the new version following the standard upgrade procedure
- Restart the MDaemon service after installation
- Verify the webmail interface is functioning correctly and the CC parameter is no longer vulnerable to XSS
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29975 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-29975 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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