# CVE-2024-11717: Business logic in CTFd

> An on-path attacker can reuse activation or reset tokens to take over user accounts and expose email addresses due to flawed token handling logic.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jan 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-9w6g-7jpw-87hf

## What is CVE-2024-11717?

CVE-2024-11717 is a medium-severity vulnerability in CTFd, published on 2 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tokens in CTFd used for account activation and password resetting can be used interchangeably for these operations. When used, they are sent to the server as a GET parameter and they are not single use, which means, that during token expiration time an on-path attacker might reuse such a token to change user's password and take over the account. Moreover, the tokens also include base64 encoded user email.

This issue impacts releases up to 3.7.4 and was addressed by  pull request 2679 https://github.com/CTFd/CTFd/pull/2679  included in 3.7.5 release.

Weakness: CWE-837 (Improper Enforcement of a Single, Unique Action), CWE-1391 (Use of Weak Credentials)

## Which versions are affected by CVE-2024-11717?


## How do I fix CVE-2024-11717?

No fix has been published for CVE-2024-11717 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-11717 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11717 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11717 and fix it if it is affected.

What it is: CVE-2024-11717 is a medium-severity vulnerability in CTFd, published on 2 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11717 exists.

Affected product: CTFd. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-11717/ (Markdown: https://insights.sbomify.com/CVE-2024-11717/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-11717
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-11717
- OSV: https://osv.dev/vulnerability/CVE-2024-11717

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-11717/
Summaries are generated and may contain mistakes; the official description above is the record.