dbcve.org
RaidenmaildApplication

CVE-2022-41676

MEDIUM · 5.4 CVSS v3.1 Published 2022-11-29
Fix available
A fix is available. Upgrade to 4.7.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Raiden MAILD Mail Server website mail field has insufficient filtering for user input. A remote attacker with general user privilege can send email using the website with malicious JavaScript in the input field, which triggers XSS (Reflected Cross-Site Scripting) attack to the mail recipient.

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 confidence

Raiden MAILD Mail Server contains a reflected XSS vulnerability in the web interface's mail input field. An authenticated user with general privileges can inject malicious JavaScript into the mail field when composing emails through the web portal. When recipients view the crafted email, the embedded JavaScript executes in their browser session, potentially allowing session hijacking or credential theft.

MitigationImplement robust input validation and sanitization for the mail field, combined with proper output encoding when rendering email content. Additionally, deploy Content-Security-Policy headers to mitigate XSS execution.

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
RaidenmaildApplication
Affected:< 4.7.4

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
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 checks

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

  1. Identify installed Raidenmaild version
    Check the Raidenmaild version through the web admin interface (usually at /admin or /webmail/admin) under 'About' or 'System Information', or query the service directly via command line if available (e.g., raidenmaild -v, or check installed package version)
    Affected if Installed version is lower than 4.7.4 (e.g., 4.7.3, 4.6.x, etc.)
  2. Confirm webmail interface is accessible
    Verify that the Raidenmaild web portal is reachable by attempting to access the login page (typically at /webmail or /mail)
    Affected if Web interface is exposed and reachable (this is required for the XSS to be exploitable)
  3. Check for regular user accounts
    Review user accounts in the Raidenmaild admin panel under 'Users' or 'Accounts' to identify accounts with general/regular privileges (non-admin users)
    Affected if There are authenticated users with general privileges (the attacker needs a standard user account to exploit this flaw)
  4. Inspect mail logs for suspicious input
    Review Raidenmaild mail logs (typically in /var/log/raidenmaild/ or via the web admin logs section) for patterns like '<script>', 'javascript:', or HTML tags in the mail input fields
    Affected if Logs showunescaped HTML/script tags in email composition records, indicating potential exploitation attempts

You are affected if your Raidenmaild version is below 4.7.4, the web interface is accessible, and you have non-admin user accounts that can compose emails through the web portal.

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 4.7.4 or later
Fixed in 4.7.4
Interim mitigation

Implement robust input validation and sanitization for the mail field, combined with proper output encoding when rendering email content. Additionally, deploy Content-Security-Policy headers to mitigate XSS execution.

Recommended fix High confidence

4.7.4 or later

  1. Identify the current Raidenmaild version by accessing the server admin panel or checking system information
  2. Navigate to the official Raidenmaild vendor website or trusted download source
  3. Download Raidenmaild version 4.7.4 or a later stable release
  4. Before upgrading, backup the current mail server configuration and data
  5. Follow the vendor's documented upgrade procedure to install the new version
  6. After upgrade, verify the version has been updated successfully
  7. Test that the website mail field properly handles special characters and prevents XSS execution

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

Fix this in Raidenmaild Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41676 — 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-2022-41676 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