dbcve.org
MoodleCMS

CVE-2024-34007

HIGH · 8.8 CVSS v3.1 Published 2024-05-31
Fix available
A fix is available. Upgrade to 4.3.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
The logout option within MFA did not include the necessary token to avoid the risk of users inadvertently being logged out via CSRF.

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 confidence

This is a CSRF (Cross-Site Request Forgery) vulnerability in the Multi-Factor Authentication (MFA) logout functionality. The logout endpoint lacks anti-CSRF token validation, allowing attackers to craft malicious requests that force authenticated users to log out without their consent. This occurs because the logout form/action does not include a unique, session-bound token that the server validates on submission.

MitigationImplement anti-CSRF tokens (e.g., synchronizer token pattern) on all state-changing operations including the MFA logout functionality. The server must validate the token before processing the logout request.

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
MoodleCMS
Affected:>= 4.3.0, < 4.3.4

CVSS 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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Moodle version
    Navigate to Site Administration > Server > Environment or check the version.php file in the Moodle root directory. Compare the installed version against the affected range: 4.3.0 to 4.3.3.
    Affected if The installed version is >= 4.3.0 and < 4.3.4
  2. Verify MFA plugin is enabled
    Go to Site Administration > Plugins > Authentication > Manage Authentication and check if the MFA authentication plugin is enabled and configured.
    Affected if MFA authentication is enabled and users are enrolled in MFA workflows
  3. Inspect logout form for CSRF token
    Enable developer tools in your browser, log in with MFA, trigger a logout, and examine the HTML of the logout form or POST request. Look for a hidden input field containing a token (commonly named sesskey, token, or similar) in the logout form/action.
    Affected if The logout form contains no hidden CSRF token field, or the POST request does not include a unique session-bound token parameter
  4. Check server-side token validation
    Review the server-side code for the logout handler (typically in /login/logout.php or related MFA logout controller). Verify whether the code extracts and validates a CSRF token before processing the logout request.
    Affected if The logout handler does not validate any anti-CSRF token before processing the logout action

You are affected if your Moodle version is 4.3.0 through 4.3.3, MFA is enabled, and the logout functionality lacks CSRF token validation on both the form and server-side.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.3.4 or later
Fixed in 4.3.4
Interim mitigation

Implement anti-CSRF tokens (e.g., synchronizer token pattern) on all state-changing operations including the MFA logout functionality. The server must validate the token before processing the logout request.

Recommended fix High confidence

Moodle 4.3.4

  1. 1. Back up your existing Moodle database and codebase before proceeding with any upgrade
  2. 2. Download Moodle version 4.3.4 or later from the official Moodle repository (download.moodle.org)
  3. 3. Replace the existing Moodle files with the new version, preserving your config.php and any custom modifications
  4. 4. Run the Moodle upgrade script by accessing your site URL (e.g., yourmoodle.com/admin) in a web browser
  5. 5. Follow the on-screen upgrade prompts to complete the database schema updates
  6. 6. Clear all Moodle caches after upgrade via Site Administration > Development > Purge caches
  7. 7. Verify the MFA logout functionality works correctly and test that the CSRF token is now properly included

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Moodle Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34007 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-34007 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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