dbcve.org
MoodleCMS

CVE-2024-34002

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
In a shared hosting environment that has been misconfigured to allow access to other users' content, a Moodle user with both access to restore feedback modules and direct access to the web server outside of the Moodle webroot could execute a local file include.

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

Moodle contains a local file inclusion vulnerability where users with access to restore feedback modules and direct access to the web server outside the Moodle webroot can include local files. This requires a misconfigured shared hosting environment that allows access to other users' content, making it a context-dependent LFI rather than a straightforward application flaw.

MitigationEnsure shared hosting environments are properly configured to prevent cross-user content access, and verify that Moodle's file path validation in restore functionality adequately restricts file inclusion to expected directories.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

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

  1. Check installed Moodle version
    Locate the version.php file in your Moodle installation root directory (usually /lib/version.php or check the version number shown on the admin dashboard at /admin/). Compare the $release or $version variable to the affected ranges.
    Affected if The installed version is < 4.1.10, OR >= 4.2.0 and < 4.2.7, OR > 4.3.0 and < 4.3.4
  2. Identify users with feedback restore permissions
    In Moodle admin, go to Users > Permissions > Assign system roles or check the 'restore' capability within the Feedback module context. Look for roles that include the 'mod/feedback:restore' or equivalent restore capability.
    Affected if Any user role has access to restore feedback modules and can perform restore operations
  3. Verify web server access beyond Moodle webroot
    Test whether the web server can serve files from directories outside the Moodle webroot. On Linux, check if file permissions and web server configuration (e.g., Apache vhost or nginx config) allow traversal to parent directories or other user directories in a shared hosting setup. Attempt to access a test file placed in a parent directory via browser.
    Affected if The web server can directly serve files from paths outside the Moodle installation directory (indicating a misconfigured shared hosting environment)

You are affected if your Moodle version is in the vulnerable range AND you have users with feedback restore capabilities operating in a shared hosting environment where the web server can access files outside the Moodle webroot.

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

Ensure shared hosting environments are properly configured to prevent cross-user content access, and verify that Moodle's file path validation in restore functionality adequately restricts file inclusion to expected directories.

Recommended fix High confidence

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

  1. 1. Identify the currently installed Moodle version by checking the version.php file in the Moodle root directory
  2. 2. Based on the current version, determine the appropriate upgrade path to a fixed release:
  3. - If using Moodle 4.1.x: upgrade to 4.1.10 or later
  4. - If using Moodle 4.2.x: upgrade to 4.2.7 or later
  5. - If using Moodle 4.3.x: upgrade to 4.3.4 or later
  6. 3. Before upgrading, take a complete backup of the Moodle database and the Moodle directory (including moodledata if external)
  7. 4. Review the Moodle upgrade documentation for your specific upgrade path at https://docs.moodle.org/401/en/Upgrading
  8. 5. Place the site into maintenance mode via Site administration > Server > Maintenance mode
Caveat Standard Moodle upgrade risks apply - always test in staging first; major version jumps may require reviewing plugin compatibility

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 / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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