CVE-2024-34008: Moodle CSRF risk in analytics management of models

moodle/moodle Updated 02 Oct 2025

Summary

31/05/2024
Yes i
High
8.8

CVE-2024-34008: Moodle CSRF risk in analytics management of models. Affects moodle/moodle across 3 version ranges.

< 4.1.10 >= 4.2.0, < 4.2.7 >= 4.3.0, < 4.3.4

Fixed in 4.1.10, 4.2.7 or 4.3.4, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2024-34008 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Moodle is an open-source learning management system (LMS) used for creating and delivering online courses. It provides various features for course management, content creation, and assessment. The Moodle package, available on Packagist, is a composer package that allows users to install and manage Moodle on their systems. This vulnerability affects versions 4.1.10 to 4.3.4 of the Moodle package.

Vulnerability Detail

The vulnerability identified as CVE-2024-34008 is a Cross-Site Request Forgery (CSRF) risk in the analytics management of models in Moodle. The admin management actions for analytics models did not include the necessary token to prevent CSRF attacks. This could allow an attacker to trick an authenticated admin user into performing unintended actions on the system, potentially leading to unauthorized access, data manipulation, or other malicious activities.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 4.1.10 4.1.10
    composer require moodle/moodle:4.1.10
  • >= 4.2.0, < 4.2.7 4.2.7
    composer require moodle/moodle:4.2.7
  • >= 4.3.0, < 4.3.4 4.3.4
    composer require moodle/moodle:4.3.4

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability.

Conclusion

The CSRF risk in the analytics management of models in Moodle can be mitigated by upgrading to the latest version of the Moodle package. It is important to stay updated with the latest security patches to ensure the integrity and security of your Moodle installation. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for moodle/moodle →

Share this vulnerability

FAQ

Moodle is an open-source learning management system used for creating and delivering online courses.

A CSRF vulnerability allows an attacker to trick an authenticated user into performing unintended actions on a web application.

The CSRF vulnerability in the analytics management of models in Moodle could lead to unauthorized access, data manipulation, or other malicious activities.

You can use Vulert's playground (https://vulert.com/scanner) to check if your Moodle installation is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just the composer.lock file.

Related vulnerabilities

Recent vulnerabilities recorded for moodle/moodle.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 4.1.10 4.1.10
    composer require moodle/moodle:4.1.10
  • >= 4.2.0, < 4.2.7 4.2.7
    composer require moodle/moodle:4.2.7
  • >= 4.3.0, < 4.3.4 4.3.4
    composer require moodle/moodle:4.3.4

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback