Moodle 4.3
Moodle 4.3
The Moodle 4.3 reached end of service life on Apr 21, 2025 — 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.3 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.3
- product Label
- Moodle
- release Label
- 4.3
- codename
- lts
- latest Version
- 4.3.12
- release Date
- 2023-10-07
- maintained
- source Url
- https://endoflife.date/moodle
Lifecycle Dates
- End of Service Life
- Apr 21, 2025
- Last OEM Support
- Oct 7, 2024
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Moodle 4.3 — 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.3?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Moodle 4.3 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.3 Support: Frequently Asked Questions
Is the Moodle 4.3 still supported?
Moodle ended support for the Moodle 4.3 on Apr 21, 2025 — 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.3 end of service life (EOSL) date?
Moodle lists the end of service life for the Moodle 4.3 as Apr 21, 2025.
Can I keep using the Moodle 4.3 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.3 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.3
75 published CVEs affect the Moodle 4.3, including 27 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-33999 | CRITICAL | 9.8 | May 31, 2024 | The referrer URL used by MFA required additional sanitizing, rather than being used directly. |
| 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-2024-34007 | HIGH | 8.8 | May 31, 2024 | The logout option within MFA did not include the necessary token to avoid the risk of users inadvertently being logged out via CSRF. |
| CVE-2025-26525 | HIGH | 8.6 | Feb 24, 2025 | 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-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-2025-26530 | HIGH | 8.3 | Feb 24, 2025 | The question bank filter required additional sanitizing to prevent a reflected XSS risk. |
| CVE-2025-26529 | HIGH | 8.3 | Feb 24, 2025 | Description information displayed in the site administration live log required additional sanitizing to prevent a stored XSS risk. |
| CVE-2025-26533 | HIGH | 8.1 | Feb 24, 2025 | An SQL injection risk was identified in the module list filter within course search. |
| 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. |
Showing the 20 most severe of 75 known CVEs.
Get Third Party Support