# CVE-2024-11716: Business logic in CTFd

> Authenticated users can improperly switch teams during an ongoing competition, violating assignment rules and compromising competition integrity.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jan 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-7wpf-4jwj-r2v3

## What is CVE-2024-11716?

CVE-2024-11716 is a medium-severity vulnerability in CTFd, published on 2 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

While assignment of a user to a team (bracket) in CTFd  should be possible only once, at the registration, a flaw in logic implementation allows an authenticated user to reset it's bracket and then pick a new one, joining another team while a competition is already ongoing.
This issue impacts releases from 3.7.0 up to 3.7.4 and was addressed by  pull request 2636 https://github.com/CTFd/CTFd/pull/2636  included in 3.7.5 release.

Weakness: CWE-837 (Improper Enforcement of a Single, Unique Action)

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


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

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

## Is CVE-2024-11716 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-11716 is a medium-severity vulnerability in CTFd, published on 2 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11716 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-11716/ (Markdown: https://insights.sbomify.com/CVE-2024-11716/index.md)
```

## Sources

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

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