CVE-2023-41155
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 · uneditedA Stored Cross-Site Scripting (XSS) vulnerability in the mail forwarding and replies tab in Webmin and Usermin 2.000 allows remote attackers to inject arbitrary web script or HTML via the forward to field while creating a mail forwarding rule.
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 · high confidenceA stored Cross-Site Scripting vulnerability exists in Webmin and Usermin 2.000 within the mail forwarding feature. Attackers can inject malicious JavaScript or HTML into the 'forward to' field when creating a mail forwarding rule. This payload is stored and executes when other users view the affected mail forwarding settings.
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= 2.000= 2.000CVSS 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 Webmin or Usermin versionLocate the installed Webmin or Usermin version in the product UI (typically found in the main dashboard or 'System Information' page) or via system package management tools if installed via package managerAffected if The installed version is exactly 2.000 (Webmin or Usermin)
-
Confirm mail forwarding feature is accessibleNavigate to the mail forwarding configuration area within Webmin or Usermin (typically under Mail settings or Forwarding section) and verify the feature is available and configurableAffected if The mail forwarding module is enabled and accessible to the user
-
Examine existing mail forwarding rulesReview all configured mail forwarding rules in the mail forwarding settings panel. Look specifically at the 'forward to' field(s) for any entries containing unusual characters, HTML tags, or JavaScript code patterns such as <script>, javascript:, or event handlers like onload/onerrorAffected if Any mail forwarding rule contains HTML or JavaScript code in the 'forward to' field that was not intentionally entered by an administrator
-
Check for unauthorized forwarding entriesAudit the complete list of mail forwarding destinations to identify any addresses that were not created by authorized administrators, particularly entries that appear to contain encoded or obfuscated contentAffected if Unexpected or unauthorized 'forward to' entries exist in the forwarding configuration
A user is affected if Webmin or Usermin version 2.000 is installed AND the mail forwarding feature is accessible with malicious JavaScript or HTML present in any 'forward to' field.
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 input validation and output encoding/escaping on the 'forward to' field in mail forwarding rules. Sanitize any user-supplied forwarding addresses before storage and before rendering in the UI.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41155 — 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-2023-41155 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