Educación a distancia Somos Expertos en servicios Moodle

The form to upload cohorts contained a redirect field, which was not restricted to internal URLs.

The size of users' private file uploads via email were not correctly checked, so their quota allowance could be exceeded.

Users with the "login as other users" capability (such as administrators/managers) can access other users' Dashboards, but the JavaScript those other users may have added to their Dashboard was not being escaped when being viewed by the user logging in on their behalf.

Please note that for versions 3.1 and 3.4 only, this...

Permissions were not correctly checked before loading event information into the calendar's edit event modal popup, so logged in non-guest users could view unauthorised calendar events. (Note: It was read-only access, users could not edit the events.)

Users could assign themselves an escalated role within courses or content accessed via LTI, by modifying the request to the LTI publisher site.

Links within assignment submission comments would open directly (in the same window). Although links themselves may be valid, opening within the same window and without the no-referrer header policy made them more susceptible to exploits.

There was a link to site home within the the Boost theme's secure layout, meaning students could navigate out of the page.

get_with_capability_join and get_users_by_capability were not taking context freezing into account when checking user capabilities

The 'manage groups' capability did not have the 'XSS risk' flag assigned to it, but does have that access in certain places. Note that the capability is intended for use by trusted users, and is only assigned to teachers and managers by default.

The mybackpack functionality allowed setting the URL of badges, when it should be restricted to the Mozilla Open Badges backpack URL. This resulted in the possibility of blind SSRF via requests made by the page.