Skip to main content
VulnerabilityPublished

CVE-2024-43425: moodle · remote code execution via calculated question types

Affects moodleSource CVE Database V5

0

Public exploit available (Metasploit, Exploit-DB) · 87% EPSS · CVSS 8.1 High · fixed in 4.4.2 : patch moodle as a priority.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
87.5% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.4.2, 4.3.6, 4.2.9 +1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 7 Nov 2024

  2. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  3. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by Fedora Project

    , 86 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. First Exploit-DB entry (opens in a new tab)

    Moodle 4.4.0 - Authenticated Remote Code Execution

    , 237 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade moodle to 4.4.2, 4.3.6, 4.2.9 or 4.1.12.

Affected software

ProductAffectedFixed in
moodleAffected
  • >=4.4 <4.4.2
Fixed in
  • 4.4.2
moodleAffected
  • >=4.3 <4.3.6
Fixed in
  • 4.3.6
moodleAffected
  • >=4.2 <4.2.9
Fixed in
  • 4.2.9
moodleAffected
  • <4.1.12
Fixed in
  • 4.1.12
GitHubmoodlepkg:github/moodleOther threatsAffected
  • <4.1.12
  • >=4.2 <4.2.9
  • >=4.3 <4.3.6
  • >=4.4 <4.4.2
Fixed in
  • 4.1.12
  • 4.2.9
  • 4.3.6
  • 4.4.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-43425, organizations should immediately review and restrict permissions related to adding or updating questions in Moodle, ensuring only trusted and necessary users have these capabilities. Implement strict role-based access controls (RBAC) and audit all users with elevated privileges. Monitor Moodle logs for unusual activity related to question creation or modification. If you cannot patch yet, consider disabling the calculated question types feature if feasible or applying custom input validation and sanitization on question inputs. Employ network segmentation to isolate Moodle servers and limit exposure. Regularly update Moodle installations and subscribe to Moodle security advisories for timely patch deployment. Conduct security awareness training for administrators and educators about the risks of privilege misuse. Additionally, implement web application firewalls (WAFs) with rules to detect and block suspicious payloads targeting question inputs. Finally, maintain regular backups of Moodle data and configurations to enable recovery in case of compromise.

Description

A flaw was found in Moodle. Additional restrictions are required to avoid a remote code execution risk in calculated question types. Note: This requires the capability to add/update questions.

References

Community reviews

Loading reviews…