How severe is CVE-2019-16662?

No CVSS score has been assigned to CVE-2019-16662 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2019-16662?

Affected package information for CVE-2019-16662 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2019-16662?

No fixed release is recorded for CVE-2019-16662 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2019-16662 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2019-16662 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2019-16662 actively exploited in the wild?

Yes. There are 9 known exploit references for CVE-2019-16662, including 2 documented proof-of-concept exploits on Exploit-DB and 6 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-16662?

CVE-2019-16662 has an EPSS (Exploit Prediction Scoring System) score of 97.7%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2019-16662?

CVE-2019-16662 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2019-16662?

A Nuclei detection template exists for CVE-2019-16662, meaning automated scanners can fingerprint it. A Metasploit module references CVE-2019-16662, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2019-16662 published, and has it been updated?

CVE-2019-16662 was published on October 28, 2019 and was last updated on August 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2019-16662 — Mhaskar

CVE-2019-16662 is a OS Command Injection vulnerability. 9 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

An issue was discovered in rConfig 3.9.2. An attacker can directly execute system commands by sending a GET request to ajaxServerSettingsChk.php because the rootUname parameter is passed…

Published

Oct 28, 2019

Updated

Aug 5, 2024

Affected

1 product

Patched

See advisory

Exploits

9 known

Exploitation data as of Oct 25, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

97.7%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

An issue was discovered in rConfig 3.9.2. An attacker can directly execute system commands by sending a GET request to ajaxServerSettingsChk.php because the rootUname parameter is passed to the exec function without filtering, which can lead to command execution.

Affected Products

1 product · 1 configurations

Application

rconfigrconfig

1 version

3.9.2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-47602remotelinux✓ Verified

rConfig - install Command Execution (Metasploit)

by Metasploit · Nov 8, 2019

Exploit-DB Source

EDB-47555webappsphp

rConfig 3.9.2 - Remote Code Execution

by Askar · Oct 29, 2019

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2019-16662 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

How to detect CVE-2019-16662

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2019-16662 -u https://target

Template: rConfig 3.9.2 - Remote Code Execution
Severity: critical
Impact: Successful exploitation of this vulnerability can lead to unauthorized access, data theft, and complete compromise of the affected system.
Remediation: Upgrade to a patched version of rConfig (3.9.3 or later) or apply the vendor-supplied patch to mitigate this vulnerability.

Template by ProjectDiscovery nuclei-templates (pikpikcu), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-16662 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works