CVE-2024-24771
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpen Forms allows users create and publish smart forms. Versions prior to 2.2.9, 2.3.7, 2.4.5, and 2.5.2 contain a non-exploitable multi-factor authentication weakness. Superusers who have their credentials (username + password) compromised could potentially have the second-factor authentication bypassed if an attacker somehow managed to authenticate to Open Forms. The maintainers of Open Forms do not believe it is or has been possible to perform this login. However, if this were possible, the victim's account may be abused to view (potentially sensitive) submission data or have been used to impersonate other staff accounts to view and/or modify data. Three mitigating factors to help prevent exploitation include: the usual login page (at `/admin/login/`) does not fully log in the user until the second factor was succesfully provided; the additional non-MFA protected login page at `/api/v2/api-authlogin/` was misconfigured and could not be used to log in; and there are no additional ways to log in. This also requires credentials of a superuser to be compromised to be exploitable. Versions 2.2.9, 2.3.7, 2.4.5, and 2.5.2 contain the following patches to address these weaknesses: Move and only enable the API auth endpoints (`/api/v2/api-auth/login/`) with `settings.DEBUG = True`. `settings.DEBUG = True` is insecure and should never be applied in production settings. Additionally, apply a custom permission check to the hijack flow to only allow second-factor-verified superusers to perform user hijacking.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpen Forms had a misconfigured non-MFA-protected API login endpoint (`/api/v2/api-authlogin/`) that could have allowed bypassing second-factor authentication if an attacker had compromised superuser credentials. Additionally, the user hijack feature lacked proper permission checks. The normal admin login requires 2FA, and the API endpoint was reportedly non-functional. The patches restrict API auth to DEBUG=True and add permission checks requiring 2FA-verified superusers for hijacking.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.2.9>= 2.3.0, < 2.3.7>= 2.4.0, < 2.4.5>= 2.5.0, < 2.5.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Open Forms versionLocate the version file or check the running application version (typically in admin UI footer, version.py, or package metadata)Affected if Version is < 2.2.9, or >= 2.3.0 and < 2.3.7, or >= 2.4.0 and < 2.4.5, or >= 2.5.0 and < 2.5.2
-
Verify DEBUG setting in configurationInspect the Django settings file (settings.py, .env, or environment variables) for the DEBUG flagAffected if DEBUG is set to True - this enables the vulnerable API authentication endpoint
-
Confirm API authentication endpoint exposureAttempt a request to /api/v2/api-authlogin/ or inspect server routing configuration to verify the endpoint is accessibleAffected if The endpoint responds (even with an error) and DEBUG=True is enabled, indicating the vulnerable endpoint is exposed
-
Check for hijack permission configurationReview the Open Forms admin settings or backend configuration for user hijack feature permissionsAffected if Hijack functionality is available to users without verified 2FA on superuser accounts
You are affected if your installed version falls within the affected ranges and DEBUG mode is enabled, exposing the non-MFA-protected API login endpoint.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.2.92.3.72.4.5
Upgrade to versions 2.2.9, 2.3.7, 2.4.5, 2.5.2 or later. Never enable DEBUG mode in production. Ensure strong credential practices to prevent initial compromise of superuser accounts.
Upgrade to 2.2.9, 2.3.7, 2.4.5, or 2.5.2 (or latest 2.x release) based on your current version branch
- Identify the currently installed Open Forms version to determine which upgrade path applies
- If running < 2.2.9: upgrade to version 2.2.9 or later
- If running >= 2.3.0 and < 2.3.7: upgrade to version 2.3.7 or later in the 2.3.x series
- If running >= 2.4.0 and < 2.4.5: upgrade to version 2.4.5 or later in the 2.4.x series
- If running >= 2.5.0 and < 2.5.2: upgrade to version 2.5.2 or later in the 2.5.x series
- After upgrade, verify that `settings.DEBUG` is NOT set to True in production environments
- Review user permissions and superuser accounts to ensure only necessary users have elevated privileges
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24771 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-24771 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data