CVE-2023-41158
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 MIME type programs tab in Usermin 2.000 allows remote attackers to inject arbitrary web script or HTML via the description field while creating a new MIME type program.
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 confidenceStored XSS vulnerability in Usermin 2.000 allows remote attackers to inject arbitrary JavaScript/HTML through the description field when creating a new MIME type program. The malicious payload persists and executes when other users view the MIME type programs tab.
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.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.
-
Confirm Usermin is installedCheck if the Usermin service or web interface is running on your system. Look for process listings or service status that includes 'usermin'.Affected if Usermin is installed and running on the system
-
Verify the Usermin versionAccess the Usermin web interface or check the installed package version. Common methods include checking the package manager, the Usermin configuration files, or the web login page version display.Affected if The installed version is exactly 2.000
-
Confirm MIME type program feature accessCheck if you can access the MIME type program configuration section in Usermin. This is typically found under the Usermin configuration or system settings related to file types or MIME handling.Affected if The MIME type program feature is accessible to the user
-
Inspect MIME type program configurationsReview any existing MIME type program entries in the Usermin configuration. Look at the description fields of configured MIME type programs for unexpected or suspicious content such as script tags, event handlers, or encoded payloads.Affected if Any MIME type program entry contains JavaScript or HTML tags in the description field that did not originate from legitimate administrative input
A system is affected if it runs Usermin version 2.000 with the MIME type program feature accessible, and either the version matches exactly or suspicious XSS payloads are found in MIME type program descriptions.
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 · scopedImplement input validation and output encoding for the description field in MIME type program creation. Sanitize or escape special characters before rendering user-supplied content.
Usermin 2.001 or later stable release
- 1. Identify your current Usermin version using the 'usermin --version' command or through the web interface
- 2. Navigate to the official Webmin/Usermin download page at webmin.com or the GitHub repository
- 3. Download the latest stable Usermin release (version 2.001 or later, as 2.000 is specifically affected)
- 4. Back up your current Usermin configuration directory (/etc/usermin or /usr/local/usermin)
- 5. Install the new version using your system's package manager or the provided installer script
- 6. Verify the MIME type programs functionality works correctly after upgrade
- 7. Confirm the stored XSS vulnerability is remediated by testing the description field in MIME type program creation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41158 — 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-41158 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