CVE-2023-41157
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 · uneditedMultiple stored cross-site scripting (XSS) vulnerabilities in Usermin 2.000 allow remote attackers to inject arbitrary web script or HTML via the folder name parameter while creating the folder to manage the folder tab, filter tab, and forward mail tab.
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 confidenceUsermin 2.000 contains multiple stored XSS vulnerabilities where remote attackers can inject arbitrary web script or HTML through the folder name parameter when creating folders. The vulnerability affects three separate functions: the folder management tab, filter tab, and forward mail tab. Since this is stored XSS, the malicious payload persists and executes when other users interact with the affected folders.
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 installation and versionCheck the installed Usermin version using the package manager (e.g., rpm -q usermin, dpkg -l usermin) or access the Usermin configuration interface and look for the version number in the main page or about section.Affected if The installed version is exactly 2.000 (not newer or older versions)
-
Identify enabled Usermin modulesAccess the Usermin configuration and review which modules are enabled. Specifically check for: 1) Folder management module, 2) Filter module, 3) Forward mail module. These are typically found under the module configuration or user access settings.Affected if Any of the three vulnerable modules (folder management, filter, or forward mail) are enabled for users
-
Review folder configuration accessCheck if regular users have permission to create or manage mail folders through Usermin. This can be verified in the Usermin module access control settings for each user or group.Affected if Users have permissions to create or manage folders via the affected interfaces
-
Inspect existing folder names for malicious contentReview the mail folder configurations and examine stored folder names in the configuration files or through the folder management interface. Look for any folder names containing script tags, HTML elements, or suspicious encoded content.Affected if Any folder names contain script tags, HTML tags, or suspicious JavaScript-like content (e.g., <script, onerror=, javascript:)
You are affected if Usermin version is exactly 2.000 AND at least one of the three vulnerable modules (folder management, filter, or forward mail) is enabled and accessible to users who can create folders.
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 folder name parameter across all three affected tabs (folder management, filter, and forward mail). Consider using a whitelist approach for folder names and ensuring all user-supplied data is sanitized before storage and display.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41157 — 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-41157 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