Moodle 4.0
Moodle 4.0
The Moodle 4.0 reached end of service life on Nov 13, 2023 — Moodle no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your Moodle 4.0 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- moodle
- release
- 4.0
- product Label
- Moodle
- release Label
- 4.0
- codename
- lts
- latest Version
- 4.0.12
- release Date
- 2022-04-17
- maintained
- source Url
- https://endoflife.date/moodle
Lifecycle Dates
- End of Service Life
- Nov 13, 2023
- Last OEM Support
- May 8, 2023
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Moodle 4.0 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Moodle 4.0?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Moodle 4.0 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Moodle 4.0 Support: Frequently Asked Questions
Is the Moodle 4.0 still supported?
Moodle ended support for the Moodle 4.0 on Nov 13, 2023 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the Moodle 4.0 end of service life (EOSL) date?
Moodle lists the end of service life for the Moodle 4.0 as Nov 13, 2023.
Can I keep using the Moodle 4.0 after its EOSL date?
Yes. EOSL means Moodle stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Moodle 4.0 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Moodle 4.0
104 published CVEs affect the Moodle 4.0, including 32 rated critical or high severity. Moodle no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2023-28333 | CRITICAL | 9.8 | Mar 23, 2023 | The Mustache pix helper contained a potential Mustache injection risk if combined with user input (note: This did not appear to be implemented/exploitable anywhere in the core Moodle LMS). |
| CVE-2022-40315 | CRITICAL | 9.8 | Sep 30, 2022 | A limited SQL injection risk was identified in the "browse list of users" site administration page. |
| CVE-2022-40314 | CRITICAL | 9.8 | Sep 30, 2022 | A remote code execution risk when restoring backup files originating from Moodle 1.9 was identified. |
| CVE-2022-35649 | CRITICAL | 9.8 | Jul 25, 2022 | The vulnerability was found in Moodle, occurs due to improper input validation when parsing PostScript code. An omitted execution parameter results in a remote code execution risk for sites running GhostScript versions older than 9.50. Successful exploitation of this vulnerability may result in complete compromise of vulnerable system. |
| CVE-2022-30600 | CRITICAL | 9.8 | May 18, 2022 | A flaw was found in moodle where logic used to count failed login attempts could result in the account lockout threshold being bypassed. |
| CVE-2022-30599 | CRITICAL | 9.8 | May 18, 2022 | A flaw was found in moodle where an SQL injection risk was identified in Badges code relating to configuring criteria. |
| CVE-2022-45152 | CRITICAL | 9.1 | Nov 25, 2022 | A blind Server-Side Request Forgery (SSRF) vulnerability was found in Moodle. This flaw exists due to insufficient validation of user-supplied input in LTI provider library. The library does not utilise Moodle's inbuilt cURL helper, which resulted in a blind SSRF risk. An attacker can send a specially crafted HTTP request and trick the application to initiate requests to arbitrary systems. This vulnerability allows a remote attacker to perform SSRF attacks. |
| CVE-2025-67847 | HIGH | 8.8 | Jan 23, 2026 | 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. |
| CVE-2025-3642 | HIGH | 8.8 | Apr 25, 2025 | A flaw was found in Moodle. A remote code execution risk was identified in the Moodle LMS EQUELLA repository. By default, this was only available to teachers and managers on sites with the EQUELLA repository enabled. |
| CVE-2025-3641 | HIGH | 8.8 | Apr 25, 2025 | A flaw was found in Moodle. A remote code execution risk was identified in the Moodle LMS Dropbox repository. By default, this was only available to teachers and managers on sites with the Dropbox repository enabled. |
| CVE-2025-3638 | HIGH | 8.8 | Apr 25, 2025 | A flaw was found in Moodle. The analysis request action in the Brickfield tool did not include the necessary token to prevent a Cross-site request forgery (CSRF) risk. |
| CVE-2024-38276 | HIGH | 8.8 | Jun 18, 2024 | Incorrect CSRF token checks resulted in multiple CSRF risks. |
| CVE-2024-34008 | HIGH | 8.8 | May 31, 2024 | Actions in the admin management of analytics models did not include the necessary token to prevent a CSRF risk. |
| CVE-2023-28329 | HIGH | 8.8 | Mar 23, 2023 | Insufficient validation of profile field availability condition resulted in an SQL injection risk (by default only available to teachers and managers). |
| CVE-2022-2986 | HIGH | 8.8 | Oct 6, 2022 | Enabling and disabling installed H5P libraries did not include the necessary token to prevent a CSRF risk. |
| CVE-2024-34001 | HIGH | 8.4 | May 31, 2024 | Actions in the admin preset tool did not include the necessary token to prevent a CSRF risk. |
| CVE-2023-23923 | HIGH | 8.2 | Feb 17, 2023 | The vulnerability was found Moodle which exists due to insufficient limitations on the "start page" preference. A remote attacker can set that preference for another user. The vulnerability allows a remote attacker to gain unauthorized access to otherwise restricted functionality. |
| CVE-2025-67848 | HIGH | 8.1 | Feb 3, 2026 | A flaw was found in Moodle. This authentication bypass vulnerability allows suspended users to authenticate through the Learning Tools Interoperability (LTI) Provider. The issue arises from the LTI authentication handlers failing to enforce the user's suspension status, enabling unauthorized access to the system. This can lead to information disclosure or other unauthorized actions by users who should be restricted. |
| CVE-2024-43434 | HIGH | 8.1 | Nov 7, 2024 | The bulk message sending feature in Moodle's Feedback module's non-respondents report had an incorrect CSRF token check, leading to a CSRF vulnerability. |
| CVE-2024-43425 | HIGH | 8.1 | Nov 7, 2024 | 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. |
Showing the 20 most severe of 104 known CVEs.
Get Third Party Support