Moodle 4.2
Moodle 4.2
The Moodle 4.2 reached end of service life on Oct 7, 2024 — 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.2 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.2
- product Label
- Moodle
- release Label
- 4.2
- codename
- lts
- latest Version
- 4.2.11
- release Date
- 2023-04-22
- maintained
- source Url
- https://endoflife.date/moodle
Lifecycle Dates
- End of Service Life
- Oct 7, 2024
- Last OEM Support
- Apr 22, 2024
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Moodle 4.2 — 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.2?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Moodle 4.2 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.2 Support: Frequently Asked Questions
Is the Moodle 4.2 still supported?
Moodle ended support for the Moodle 4.2 on Oct 7, 2024 — 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.2 end of service life (EOSL) date?
Moodle lists the end of service life for the Moodle 4.2 as Oct 7, 2024.
Can I keep using the Moodle 4.2 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.2 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.2
64 published CVEs affect the Moodle 4.2, including 17 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-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-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-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. |
| CVE-2024-43428 | HIGH | 7.7 | Nov 7, 2024 | To address a cache poisoning risk in Moodle, additional validation for local storage was required. |
| CVE-2024-45690 | HIGH | 7.5 | Nov 20, 2024 | A flaw was found in Moodle. Additional checks were required to ensure users can only delete their OAuth2-linked accounts. |
| CVE-2024-43440 | HIGH | 7.5 | Nov 7, 2024 | A flaw was found in moodle. A local file may include risks when restoring block backups. |
| CVE-2024-43438 | HIGH | 7.5 | Nov 7, 2024 | A flaw was found in Feedback. Bulk messaging in the activity's non-respondents report did not verify message recipients belonging to the set of users returned by the report. |
| CVE-2024-43431 | HIGH | 7.5 | Nov 7, 2024 | A vulnerability was found in Moodle. Insufficient capability checks made it possible to delete badges that a user does not have permission to access. |
| CVE-2024-43426 | HIGH | 7.5 | Nov 7, 2024 | A flaw was found in pdfTeX. Insufficient sanitizing in the TeX notation filter resulted in an arbitrary file read risk on sites where pdfTeX is available, such as those with TeX Live installed. |
| CVE-2024-38275 | HIGH | 7.5 | Jun 18, 2024 | The cURL wrapper in Moodle retained the original request headers when following redirects, so HTTP authorization header information could be unintentionally sent in requests to redirect URLs. |
| CVE-2024-25978 | HIGH | 7.5 | Feb 19, 2024 | Insufficient file size checks resulted in a denial of service risk in the file picker's unzip functionality. |
| CVE-2023-35133 | HIGH | 7.5 | Jun 22, 2023 | An issue in the logic used to check 0.0.0.0 against the cURL blocked hosts lists resulted in an SSRF risk. This flaw affects Moodle versions 4.2, 4.1 to 4.1.3, 4.0 to 4.0.8, 3.11 to 3.11.14, 3.9 to 3.9.21 and earlier unsupported versions. |
| CVE-2026-26046 | HIGH | 7.2 | Feb 21, 2026 | A vulnerability was found in a Moodle TeX filter administrative setting where insufficient sanitization of configuration input could allow command injection. On sites where the TeX filter is enabled and ImageMagick is installed, a maliciously crafted setting value entered by an administrator could result in unintended system command execution. While exploitation requires administrative privileges, successful compromise could affect the entire Moodle server. |
| CVE-2026-26045 | HIGH | 7.2 | Feb 21, 2026 | A flaw was identified in Moodle’s backup restore functionality where specially crafted backup files were not properly validated during processing. If a malicious backup file is restored, it could lead to unintended execution of server-side code. Since restore capabilities are typically available to privileged users, exploitation requires authenticated access. Successful exploitation could result in full compromise of the Moodle server. |
| CVE-2024-43436 | HIGH | 7.2 | Nov 7, 2024 | A SQL injection risk flaw was found in the XMLDB editor tool available to site administrators. |
| CVE-2026-26047 | MEDIUM | 6.5 | Feb 21, 2026 | A denial-of-service vulnerability was identified in Moodle’s TeX formula editor. When rendering TeX content using mimetex, insufficient execution time limits could allow specially crafted formulas to consume excessive server resources. An authenticated user could abuse this behavior to degrade performance or cause service interruption. |
| CVE-2024-45689 | MEDIUM | 6.5 | Nov 20, 2024 | A flaw was found in Moodle. Dynamic tables did not enforce capability checks, which resulted in users having the ability to retrieve information they did not have permission to access. |
| CVE-2024-34005 | MEDIUM | 6.5 | May 31, 2024 | In a shared hosting environment that has been misconfigured to allow access to other users' content, a Moodle user with both access to restore database activity modules and direct access to the web server outside of the Moodle webroot could execute a local file include. |
Showing the 20 most severe of 64 known CVEs.
Get Third Party Support