CVE-2023-41152
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 handle program 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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in Usermin 2.000 where the 'handle program' field in the MIME type programs tab does not properly sanitize user input. When creating a new MIME type program, malicious JavaScript or HTML injected into this field is stored and executed when other users view the MIME type configuration.
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 versionCheck the installed Usermin version. This is typically displayed in the Usermin login page footer, or can be found in the package manager (e.g., dpkg -l usermin, rpm -qi usermin, or checking /usr/lib/usermin/version).Affected if The version is exactly 2.000 (other versions are not affected by this specific CVE).
-
Locate MIME type programs configurationAccess the Usermin web interface and navigate to the MIME Type Programs configuration. This is usually found under Usermin Configuration > MIME Types or a similar path within the Usermin settings.Affected if The MIME type programs configuration interface is accessible in the Usermin installation.
-
Identify handle program fieldsIn the MIME type programs tab, identify any entries with a 'handle program' field. These fields specify which program handles each MIME type.Affected if There are existing MIME type program entries configured, or the ability to create new ones.
-
Inspect stored handle program valuesView the existing MIME type program configurations and inspect the 'handle program' field values for any HTML, JavaScript, or suspicious encoded content. Look for script tags, event handlers (onclick, onerror, etc.), or encoded variations.Affected if The stored value contains unsanitized HTML/JavaScript that would execute when rendered.
A user is affected if they are running Usermin version 2.000 and have any MIME type program configurations where the handle program field contains unsanitized user-supplied input that could execute as JavaScript or HTML when viewed.
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 validation and output encoding for the handle program field in the MIME type program creation/update functionality to prevent XSS execution.
- 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-41152 — 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-41152 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