CVE-2023-41163
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 Reflected Cross-site scripting (XSS) vulnerability in the file manager tab in Usermin 2.000 allows remote attackers to inject arbitrary web script or HTML via the replace in results field while replacing the results under the tools drop down.
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 confidenceA reflected XSS vulnerability exists in Usermin 2.000's file manager tab. Attackers can inject malicious scripts through the 'replace in results' field under the tools dropdown. When a user performs a replace operation, the unsanitized input is reflected in the response, executing the attacker's JavaScript in 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= 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
- 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.
-
Confirm Webmin or Usermin installationCheck if Webmin/Usermin is installed by looking for its process or service. Common locations: /etc/webmin/, /usr/share/webmin/, or check systemctl status webmin. Alternatively, check for port 10000 (default Webmin port) listening.Affected if Webmin or Usermin version 2.000 is installed and running
-
Identify the exact version numberAccess the Webmin configuration page, or run: rpm -q webmin (RPM-based) or dpkg -l webmin (DEB-based). You can also check /etc/webmin/version or the Webmin login page footer which displays the version.Affected if The installed version is exactly 2.000 (this is a narrow, specific version)
-
Verify file manager module is enabledLog into Webmin/Usermin interface and check if the 'File Manager' module is available. This can also be checked via Webmin's module configuration at: /webmin/filemin/ or by examining /etc/webmin/filemin/config.Affected if File manager module is enabled and accessible to users
-
Confirm replace functionality is accessibleIn the file manager interface, navigate to the tools dropdown and locate the 'replace in results' or 'find and replace' feature. Check if regular users or administrators can access this tool.Affected if Users have access to the replace function in the file manager tools dropdown
You are affected if running Webmin/Usermin exactly version 2.000 with the file manager module enabled and the replace feature accessible to users.
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 proper output encoding/HTML escaping on user-supplied input in the replace function, and add input validation to reject or sanitize special characters before reflecting content back to the user.
Webmin/Usermin 2.001 or later (latest stable release)
- Check the current Webmin/Usermin version by navigating to the Webmin Configuration page or running 'webmin --version'
- Navigate to Webmin's official download page at webmin.com/download.html or the GitHub repository to find the latest stable release
- Download and install the latest version of Webmin/Usermin that includes the security fix for CVE-2023-41163
- After upgrade, verify the file manager's 'replace in results' functionality works correctly and the XSS vulnerability is remediated
- Consider reviewing Webmin's release notes for version 2.001 or later to confirm the security patch was included
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41163 — 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-41163 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