CVE-2024-36450
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 · uneditedCross-site scripting vulnerability exists in sysinfo.cgi of Webmin versions prior to 1.910. If this vulnerability is exploited, an arbitrary script may be executed on the web browser of the user who accessed the website using the product. As a result, a session ID may be obtained, a webpage may be altered, or a server may be halted.
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 cross-site scripting (XSS) vulnerability exists in the sysinfo.cgi component of Webmin versions prior to 1.910. The flaw allows attackers to inject arbitrary JavaScript that executes in the browsers of users accessing the affected sysinfo.cgi page, potentially enabling session hijacking, webpage defacement, or denial of service.
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< 1.910CVSS 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.
-
Verify Webmin is installedCheck for Webmin by looking for the /etc/webmin directory, running processes containing 'miniserv', or accessing the Webmin login page on port 10000Affected if Webmin is found to be installed on the system
-
Determine installed Webmin versionRun 'cat /etc/webmin/version' or check the Webmin web UI footer which displays the version numberAffected if The displayed version is lower than 1.910
-
Confirm sysinfo.cgi module is accessibleCheck if the sysinfo.cgi file exists in the Webmin CGI directory (typically /usr/libexec/webmin/sysinfo.cgi or /usr/lib/webmin/sysinfo.cgi) and is accessible via URL at /sysinfo.cgiAffected if The sysinfo.cgi file exists and responds to requests
-
Verify vulnerability conditionCompare the installed version against the affected range: any version below 1.910 is vulnerableAffected if The installed Webmin version is any version prior to 1.910 (e.g., 1.900, 1.890, 1.880, etc.)
A system is affected if Webmin is installed with any version lower than 1.910 and the sysinfo.cgi module is accessible.
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 · scoped1.910
Upgrade Webmin to version 1.910 or later to remediate this vulnerability. If immediate upgrading is not feasible, consider restricting access to sysinfo.cgi or deploying a WAF rule to filter malicious input.
Webmin 1.910 or later
- 1. Back up the current Webmin configuration and data
- 2. Download Webmin version 1.910 or later from the official Webmin website
- 3. Install the upgrade following standard Webmin upgrade procedures
- 4. Verify the installation was successful
- 5. Confirm the sysinfo.cgi page functions correctly and the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36450 — 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-2024-36450 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