CVE-2019-15642 in the critical feed json
rpc.cgi in Webmin through 1.920 allows authenticated Remote Code Execution via a crafted object name because unserialise_variable makes an…
published 7y ago modified 4mo ago also EUVD-2019-6594
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 36.6%
- EPSS 36.6% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
rpc.cgi in Webmin through 1.920 allows authenticated Remote Code Execution via a crafted object name because unserialise_variable makes an eval call. NOTE: the Webmin_Servers_Index documentation states "RPC can be used to run any command or modify any file on a server, which is why access to it must not be granted to un-trusted Webmin users."
Patch / fix
Is CVE-2019-15642 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
36.63% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template Webmin < 1.920 - Authenticated Remote Code Execution nuclei detection template
- calypt.com https://www.calypt.com/blog/index.php/authenticated-rce-on-webmin/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
github.com
/webmin/webmin/commit/df8a43fb4bdc9c858874f72773bcba597ae9432c
patch
-
calypt.com
/blog/index.php/authenticated-rce-on-webmin/
exploit, patch, third-party-advisory
-
github.com
/webmin/webmin/blob/ab5e00e41ea1ecc1e24b8f8693f3495a0abb1aed/rpc.cgi#L26-L37
patch
-
doxfer.webmin.com
/Webmin/Webmin_Servers_Index
vendor-advisory
Sources
- CVE List CVE-2019-15642
- NVD CVE-2019-15642
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.