CVE-2024-11716
Raw vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2024-11716 is a medium-severity Improper Enforcement of a Single, Unique Action (CWE-837) vulnerability in Ctfd (inferred from references). Its CVSS base score is 5.3 (Medium).
Operationally, ranked in the top 4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CTFd, an open-source capture-the-flag platform, contains a logic flaw in its team (bracket) assignment mechanism that affects versions 3.7.0 through 3.7.4. Although bracket assignment is intended to occur only once during initial registration, the implementation permits an authenticated user to reset an existing bracket assignment and select a different one after a competition has begun.
An authenticated participant can therefore exploit the issue to switch teams mid-event, potentially gaining access to another team's progress, challenges, or scoring data. The vulnerability carries a CVSS 4.0 score of 5.3 and is tracked under CWE-837 for improper enforcement of behavioral workflow.
The flaw was corrected in release 3.7.5 by pull request 2636, as noted in the CTFd 3.7.5 announcement and related advisories from CERT.pl and Full Disclosure. Administrators are advised to upgrade to the patched version to restore the intended one-time assignment restriction.
EPSS scores have remained low, with a current value of 0.0513 and a peak of 0.0658, indicating limited observed exploitation interest to date.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-34048
- 🇵🇱 CERT-PL: cert.pl
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.3.3V6.5.1V7.6.2V17.3.1
Mitigating Controls (NIST 800-53 r5) AI
AC-3 enforces approved authorizations for actions; when policy requires an action to occur only once, proper enforcement directly stops duplicate execution.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Authorization policy enforcement can include rules that restrict actions to a single use.
Logical access controls can incorporate mechanisms that block replay or repeated actions.
Preventing execution of unauthorized or duplicate actions directly addresses single-use enforcement.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Access-control rules can enforce single-use or uniqueness constraints, but the control is broader than this specific weakness.
Managing access rights can include rules that limit an action to one occurrence, yet the control addresses rights in general.
Secure SDLC practices can require design controls for single-use actions, but the control addresses the entire lifecycle.
Application-security requirements can specify single-action enforcement, yet the control is wider in scope.
Secure-coding standards can mandate checks that prevent repeated actions, but the control covers many coding issues.
Information-access-restriction mechanisms can implement single-action limits, but the control covers broader access-restriction needs.