dbcve.org
WebminApplication

CVE-2026-22678

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-21
Fix available
A fix is available. Upgrade to 2.641 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Webmin before 2.641 contains a stored cross-site scripting vulnerability in the email template description field of the System and Server Status module that allows low-privileged authenticated attackers to execute arbitrary JavaScript in the browser context of administrators by injecting unsanitized input stored in save_tmpl.cgi and rendered unescaped in list_tmpls.cgi.

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 confidence

Stored XSS vulnerability in Webmin's System and Server Status module allows low-privileged authenticated users to inject malicious JavaScript into email template description fields via save_tmpl.cgi, which then executes in administrator browsers when templates are viewed in list_tmpls.cgi due to unescaped output.

MitigationUpgrade to Webmin version 2.641 or later which implements proper input sanitization and output encoding for the template description field.

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
WebminApplication
Affected:< 2.641

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine your installed Webmin version
    Access the Webmin configuration page or run the command to retrieve the Webmin version (such as 'webmin --version' or checking the package version)
    Affected if Your Webmin version is lower than 2.641 (for example, 2.640, 2.630, etc.)
  2. Verify the System and Server Status module is present
    Check if the System and Server Status module is installed and accessible in your Webmin interface under the appropriate module listing
    Affected if The module exists and is enabled in your Webmin installation
  3. Inspect email templates for unexpected content
    Access the email template management interface (list_tmpls.cgi) or examine the underlying template storage to view the description fields of any saved templates
    Affected if You find templates with description fields containing suspicious JavaScript code, unusual HTML tags, or unexpected character sequences that were not intentionally added by an administrator
  4. Verify access controls on save_tmpl.cgi
    Confirm whether low-privileged users have the ability to access and use the save_tmpl.cgi script to create or modify email templates
    Affected if Users with limited or low-privileged accounts can access the template saving functionality

You are affected if your Webmin version is below 2.641 and you have email templates stored in the System and Server Status module that may contain malicious script content injected by low-privileged users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.641 or later
Fixed in 2.641
Interim mitigation

Upgrade to Webmin version 2.641 or later which implements proper input sanitization and output encoding for the template description field.

Recommended fix High confidence

Webmin 2.641 or later

  1. 1. Back up your current Webmin configuration and data before upgrading
  2. 2. Update Webmin to version 2.641 or later using your system's package manager or Webmin's built-in update feature
  3. 3. Verify the upgrade was successful by checking the Webmin version in the web interface (Webmin -> Webmin Configuration -> About Webmin)
  4. 4. Log in to the web interface and navigate to the System and Server Status module
  5. 5. Navigate to the email template settings and confirm that the description field now properly sanitizes input
  6. 6. Clear browser cache and test with a benign input to verify XSS filtering is working

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Webmin Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22678 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22678 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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