Moodle ≫ Moodle

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...

The site log report required additional encoding of event descriptions to ensure any HTML in the content is displayed in plaintext instead of being rendered.

The logout option within MFA did not include the necessary token to avoid the risk of users inadvertently being logged out via CSRF.

Actions in the admin management of analytics models did not include the necessary token to prevent a CSRF risk.

Insufficient checks whether ReCAPTCHA was enabled made it possible to bypass the checks on the login page. This did not affect other pages where ReCAPTCHA is utilized.

ID numbers displayed in the lesson overview report required additional sanitizing to prevent a stored XSS risk.

Actions in the admin preset tool did not include the necessary token to prevent a CSRF risk.

Incorrect validation of allowed event types in a calendar web service made it possible for some users to create events with types/audiences they did not have permission to publish to.

Additional sanitizing was required when opening the equation editor to prevent a stored XSS risk when editing another user's equation.

Insufficient escaping of participants' names in the participants page table resulted in a stored XSS risk when interacting with some features.