Skip to main content
CVE-2025-67847VulnerabilityPublished Updated

CVE-2025-67847: moodle · Code Injection

Affects moodleSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

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

    Not in CISA KEV and no source reports exploitation

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

    No attack traffic recorded by OffSeq Mirage sensors

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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Packagistmoodle/moodlepkg:composer/moodle/moodleOther threatsAffected
  • =0
  • =4.1.0
  • =4.4.0
  • =4.5.0
  • =5.0.0
  • =5.1.0
Fixed in–

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-2025-67847, organizations should immediately upgrade Moodle to a patched version once available from the official Moodle security advisories. In the interim, restrict access to the restore interface strictly to trusted administrators and monitor restore activity logs for suspicious behavior. Implement network segmentation and access controls to limit exposure of Moodle servers to only necessary personnel. Employ multi-factor authentication for all administrative accounts to reduce risk of credential compromise. Regularly audit user permissions to ensure only authorized users have restore privileges. Consider deploying web application firewalls (WAFs) with custom rules to detect and block suspicious restore requests. Conduct thorough input validation and sanitization on any custom Moodle plugins or extensions that interact with restore functionality. Maintain up-to-date backups and test restore procedures in isolated environments to prevent exploitation during recovery operations. Finally, monitor threat intelligence feeds for any emerging exploits targeting this vulnerability and respond promptly.

Description

A flaw was found in Moodle. An attacker with access to the restore interface could trigger server-side execution of arbitrary code. This is due to insufficient validation of restore input, which leads to unintended interpretation by core restore routines. Successful exploitation could result in a full compromise of the Moodle application.

References

Community reviews

Loading reviews…