dbcve.org
MoodleCMS

CVE-2024-34001

HIGH · 8.4 CVSS v3.1 Published 2024-05-31
Fix available
A fix is available. Upgrade to 4.1.10 / 4.2.7 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable

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
Actions in the admin preset tool did not include the necessary token to prevent a CSRF risk.

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 · moderate confidence

This is a Cross-Site Request Forgery (CSRF) vulnerability in an admin preset tool where form actions and state-changing requests lack anti-CSRF tokens. An attacker could trick an authenticated administrator into unknowingly executing unintended administrative actions such as creating, modifying, or deleting presets.

MitigationImplement anti-CSRF tokens (synchronizer token pattern or similar) on all state-changing actions within the admin preset tool, and ensure the server validates these tokens on each 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.1.10>= 4.2.0, < 4.2.7>= 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
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/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. Check installed Moodle version
    Log into the Moodle admin panel and navigate to Site administration > Server > System paths, or check the version.php file in the Moodle root directory. Compare the version number against the affected ranges: < 4.1.10, >= 4.2.0 and < 4.2.7, or >= 4.3.0 and < 4.3.4.
    Affected if The installed version falls within any of these ranges: < 4.1.10, >= 4.2.0 to < 4.2.7, or >= 4.3.0 to < 4.3.4.
  2. Verify admin preset tool is accessible
    Navigate to Site administration > Courses > Course presets, or check if the preset management interface is available in the admin dashboard. Determine if any preset functionality is currently in use or configured.
    Affected if The admin preset tool interface is accessible and the Moodle version is in the affected range.
  3. Inspect preset tool forms for anti-CSRF tokens
    Access the admin preset tool and use browser developer tools to examine the HTML source of forms used for creating, modifying, or deleting presets. Look for input fields containing 'sesskey' or similar token parameters in the form markup.
    Affected if The preset-related forms lack a sesskey or equivalent anti-CSRF token field in their HTML.
  4. Check server-side token validation
    Review the server-side PHP code handling preset tool requests, specifically the files in the admin/preset directory. Examine if the code validates the sesskey parameter before processing state-changing operations like create, update, or delete actions.
    Affected if The server-side code does not validate or check the sesskey parameter on preset management requests.

A user is affected if their Moodle installation version is in the vulnerable range and the admin preset tool is in use without proper anti-CSRF token protection on state-changing requests.

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.1.10 / 4.2.7 / 4.3.4 or later
Fixed in 4.1.104.2.74.3.4
Interim mitigation

Implement anti-CSRF tokens (synchronizer token pattern or similar) on all state-changing actions within the admin preset tool, and ensure the server validates these tokens on each request.

Recommended fix High confidence

Moodle 4.1.10, 4.2.7, or 4.3.4 (minimum, depending on your current branch)

  1. 1. Back up your Moodle database and all site files before proceeding
  2. 2. Download the appropriate fixed Moodle version for your branch (4.1.10+, 4.2.7+, or 4.3.4+) from moodle.org
  3. 3. Replace all Moodle core files with the new version, preserving your config.php and any customizations
  4. 4. Run the upgrade by accessing your Moodle site in a browser (or via CLI: php admin/cli/upgrade.php)
  5. 5. Clear all Moodle caches after upgrade completion
  6. 6. Verify the admin preset tool now requires tokens and test that functionality works correctly
Caveat Check Moodle release notes for your target version for any behavioral changes; major version jumps may include template/theme updates

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

Fix this in Moodle Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34001 — 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-34001 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