CVE-2022-36880
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 · uneditedThe Read Mail module in Webmin 1.995 and Usermin through 1.850 allows XSS via a crafted HTML e-mail message.
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 confidenceCross-site scripting (XSS) vulnerability in the Read Mail module of Webmin 1.995 and Usermin through 1.850 allows attackers to inject malicious scripts via crafted HTML e-mail messages. The email content is not properly sanitized before rendering, enabling script execution in the context of the victim's browser.
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<= 1.850= 1.995CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 product and versionRun command: rpm -q webmin usermin or check /etc/webmin/version for Webmin, /etc/usermin/version for UserminAffected if Version is 1.995 for Webmin or 1.850 or lower for Usermin
-
Confirm Read Mail module is accessibleCheck if mail configuration exists: ls /etc/webmin/mail/ or ls /etc/usermin/mail/ and verify the module is enabled in /etc/webmin/config or /etc/usermin/configAffected if The Read Mail module is enabled and accessible to users
-
Verify email functionality is configuredCheck for mail-related configuration files in the Webmin/Usermin config directory indicating Read Mail module has been used or configuredAffected if Email accounts or mail configuration exists, meaning users can receive and view emails through the Read Mail module
-
Check for recent module access logsReview Webmin/Usermin access logs for Read Mail module usage: grep -i 'mail' /var/webmin/ logs/access_log or equivalent log pathAffected if Users have accessed the Read Mail module to view emails, exposing them to potential XSS via malicious HTML messages
Your environment is affected if you run Webmin 1.995 or Usermin 1.850 or lower with the Read Mail module enabled and configured for users to view emails.
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.
From vendor dataImplement proper input sanitization and output encoding for email content displayed in the Read Mail module. Consider using HTML sanitization libraries to strip dangerous tags/attributes and enforce Content Security Policy headers to mitigate XSS execution.
- 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-36880 — 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-36880 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