CVE-2022-29976
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 BCC 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 the BCC parameter of MDaemon email server versions prior to 22.0.0. An attacker with valid credentials can inject malicious JavaScript code through the BCC field, which gets reflected back in the response without proper sanitization.
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.
-
Identify installed MDaemon versionLocate the MDaemon installation and check the version number, typically shown in the application GUI, About dialog, or in the MDaemon\App\version.ini file. Compare it to the affected range of versions prior to 22.0.0.Affected if The installed version is below 22.0.0
-
Confirm WorldClient webmail is enabledCheck if the WorldClient webmail interface is accessible and active. This is typically found in MDaemon configuration under WorldClient settings or by attempting to access the webmail portal on port 2000 or 443.Affected if WorldClient/webmail interface is enabled and accessible
-
Verify user account existenceCheck if there are active user accounts configured in MDaemon. The vulnerability requires valid credentials to exploit, so existence of any user accounts (especially administrative ones) enables the attack vector.Affected if Active user accounts exist in the MDaemon system
-
Test BCC parameter for XSS reflectionLog into WorldClient with a valid account and locate the BCC field in the compose email interface. Insert a test XSS payload such as <script>alert('XSS')</script> into the BCC field and observe if it is reflected unescaped in the response.Affected if The BCC field reflects input without proper HTML encoding or sanitization
The environment is affected if the installed MDaemon version is below 22.0.0, WorldClient webmail is enabled, and valid user credentials exist that could be used to inject malicious script through the BCC parameter.
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 MDaemon to version 22.0.0 or later to obtain the vendor patch. As a temporary measure, restrict administrative access and validate input in the BCC parameter until the upgrade can be performed.
MDaemon 22.0.0
- Download MDaemon version 22.0.0 or later from the official MDaemon website or your trusted distribution channel
- Review the MDaemon 22.0.0 release notes for any configuration or feature changes
- Create a complete backup of your current MDaemon configuration, settings, and mail data
- Stop the MDaemon service before upgrading
- Install MDaemon 22.0.0 following standard installation procedures
- Verify the installation completed successfully
- Start the MDaemon service
- Log in to the MDaemon web interface and verify the BCC parameter is now properly sanitized
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29976 — 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-29976 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