CSRF in Rconfig
CVE-2020-12257
rConfig 3.9.4 is vulnerable to cross-site request forgery (CSRF) because it lacks implementation of CSRF protection such as a CSRF token. An attacker can leverage this vulnerability by creating a form (add a user, delete a user, or edit a user).
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS: 0.014 (71.6th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 72nd percentile — 71.6% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.014 · newest: 0.014 · change: 0.000
Affected products
- Rconfig — versions 3.9.4
Weakness classification (CWE)
Public proof-of-concept exploits
References
- gist.github.com/farid007/eb7310749520fb8cdf5942573c9954ef (Exploit, Third Party Advisory)
Frequently asked questions
- What is CVE-2020-12257?
- CVE-2020-12257 is a high-severity vulnerability in Rconfig, classified under Cross-Site Request Forgery (CSRF). CVSS score: 8.8/10. Published 2020-05-18.
- How severe is CVE-2020-12257?
- High severity. CVSS v3 base score is 8.8 out of 10.
- Is CVE-2020-12257 known to be exploited?
- 2 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.