CVE-2020-12257: CSRF
First published: Mon May 18 2020(Updated: )
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).
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| rConfig rConfig | =3.9.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the vulnerability ID for rConfig 3.9.4?
The vulnerability ID for rConfig 3.9.4 is CVE-2020-12257.
What is the severity of CVE-2020-12257?
The severity of CVE-2020-12257 is high with a severity score of 8.8.
What is the affected software for CVE-2020-12257?
The affected software for CVE-2020-12257 is rConfig 3.9.4.
What is the vulnerability description of CVE-2020-12257?
CVE-2020-12257 is a cross-site request forgery (CSRF) vulnerability in rConfig 3.9.4.
How can an attacker exploit CVE-2020-12257?
An attacker can exploit CVE-2020-12257 by creating a form to perform unauthorized actions on the affected rConfig 3.9.4 instance.
- collector/nvd-index
- vendor/rconfig
- canonical/rconfig rconfig
- version/rconfig rconfig/3.9.4