Insufficient access checks on H5P content files could result in users, including those who were not logged in, having access to view H5P content they did not have permission to access.
Moodle 4.5.12 4.5 is supportedLTS
Released 8 Jun 2026. The current 4.5 release is 4.5.15, published 5 Oct 2026.
Every one of them is fixed in 4.5.15, the current 4.5 release, 3 releases ahead of you. Upgrading within the branch is a minor update with no feature changes.
Insufficient validation of a profile availability condition check resulted in a blind SQL injection risk being available to teachers (and other privileged users such as admins).
The XML grade import functionality (which allows setting or overwriting of student grades) did not include the necessary token to prevent a CSRF risk.
An incorrect capability check in a grade web service allowed students to access profile information of other students enrolled in the same course, which they would not otherwise have access to.
An SQL injection risk was identified in a question bank web service.
Incorrect handling of IPv4-mapped IPv6 addresses could allow bypassing of some blocked hosts, resulting in an SSRF risk.
It was possible to bypass the login notification mechanism, so a user would not be notified if their account received a new login. This could make it easier for unauthorised users to log in without detection. Note: Valid login credentials (such as username and password) were still required.
User list filters allowed managers to filter by user profile fields that they could not view on users' profiles.
Insufficient username escaping could allow a minor XSS risk if an unauthenticated user was tricked into opening a password reset link (so did not affect authenticated user sessions).
An incorrect capability check in the AI "generate image" web service could allow users to access that feature without having the "generate image" capability.
The manual enrolment management page did not prevent direct access when the plugin was disabled and a link was no longer available in the UI. Note: This still required the relevant capability to access the page (had it been enabled).
Insufficient escaping resulted in an XSS risk in some templates used to display forum posts.
Insufficient validation of the audience classname in report builder allowed arbitrary class instantiation.
Advisory titles and descriptions are Moodle's own words, from the security announcements on moodle.org, and every entry links to its source. This list is a lower bound: Moodle stops issuing advisories for a branch once it leaves security support. MDL Shield is an independent service and is not affiliated with or endorsed by Moodle Pty Ltd.