CVE-2020-10546 in the critical feed json
rConfig 3.9.4 and previous versions has unauthenticated compliancepolicies.inc.php SQL injection.
published 6y ago modified 4mo ago also EUVD-2020-2998
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 87.3%
- EPSS 87.3% chance of exploitation in 30 days, percentile 99.7%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
rConfig 3.9.4 and previous versions has unauthenticated compliancepolicies.inc.php SQL injection. Because, by default, nodes' passwords are stored in cleartext, this vulnerability leads to lateral movement, granting an attacker access to monitored network devices.
Is CVE-2020-10546 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
87.33% chance of exploitation in the next 30 days, higher than 99.7% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template rConfig 3.9.4 - SQL Injection nuclei detection template
- github.com https://github.com/theguly/exploits/blob/master/CVE-2020-10546.py referenced PoC, tagged "exploit" by a source, unverified
- theguly.github.io https://theguly.github.io/2020/09/rconfig-3.9.4-multiple-vulnerabilities/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/theguly/exploits/blob/master/CVE-2020-10546.py
exploit, third-party-advisory
-
theguly.github.io
/2020/09/rconfig-3.9.4-multiple-vulnerabilities/
exploit, third-party-advisory
Sources
- CVE List CVE-2020-10546
- NVD CVE-2020-10546
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.