dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Apr 2022. Known ransomware use
WebminApplication

CVE-2019-15107

CRITICAL · 9.8 CVSS v3.1 Published 2019-08-16
Fix available
A fix is available. Upgrade to after 1.920 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges Zero-click

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
An issue was discovered in Webmin <=1.920. The parameter old in password_change.cgi contains a command injection vulnerability.

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

Webmin versions 1.920 and below contain a command injection vulnerability in the password_change.cgi script. The 'old' parameter is not properly sanitized before being passed to the underlying system, allowing an attacker to inject arbitrary shell commands. With a CVSS score of 9.8, this vulnerability is critical severity and likely exploitable remotely without authentication.

MitigationUpgrade Webmin to a version newer than 1.920. If immediate patching is not feasible, restrict network access to password_change.cgi or disable the password change functionality until the update can be applied.

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:<= 1.920

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Verify Webmin is installed
    Check if Webmin is running by scanning for processes named 'miniserv' or by testing connectivity on port 10000 (default Webmin port)
    Affected if Webmin is found running on the system
  2. Determine Webmin version
    Access the Webmin login page and check the version displayed, or use the command line: 'rpm -q webmin' or check /etc/webmin/version
    Affected if Installed version is 1.920 or lower (or version cannot be determined but Webmin is present)
  3. Verify password_change.cgi exists
    Check if the password_change.cgi file exists in the Webmin CGI directory, typically found at /usr/libexec/webmin/password_change.cgi or /usr/share/webmin/password_change.cgi
    Affected if password_change.cgi file exists on the system
  4. Check if password change functionality is enabled
    In Webmin, go to Webmin Configuration -> Authentication and verify if password changing is allowed, or check the /etc/webmin/miniserv.conf for 'passwd_mode' setting
    Affected if Password change functionality is enabled (passwd_mode is not set to 0 or disabled)

If Webmin version 1.920 or lower is running with password_change.cgi accessible and password change functionality enabled, the system is vulnerable to CVE-2019-15107 command injection.

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 a release after 1.920
Interim mitigation

Upgrade Webmin to a version newer than 1.920. If immediate patching is not feasible, restrict network access to password_change.cgi or disable the password change functionality until the update can be applied.

Recommended fix High confidence

Webmin 1.930 or later

  1. Back up the Webmin configuration directory (typically /etc/webmin or /var/lib/webmin) and your system
  2. Update Webmin using your package manager if installed via apt/yum (e.g., 'apt update && apt install webmin' or 'yum update webmin'), OR run the webmin update script: /etc/webmin/install.pl
  3. Alternatively, download the latest Webmin version from www.webmin.com and install via: 'rpm -Uvh webmin-X.XXX.rpm' or 'dpkg -i webmin-X.XXX.deb'
  4. Restart the Webmin service after upgrade: '/etc/webmin/restart' or 'systemctl restart webmin'
  5. Verify the upgrade was successful by logging into the Webmin UI and checking the version under the 'Webmin Configuration' > 'About Webmin' page
  6. Confirm the running version is 1.930 or higher
Caveat Standard minor version upgrade; review release notes for any configuration changes. Back up before upgrading.

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

Fix this in Webmin Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-15107 — 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-2019-15107 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