Anuncis de seguretat | Moodle.org

Users with permission to delete entries from a glossary were able to delete entries from other glossaries they did not have direct access to.

A sesskey (CSRF) token was not being utilised by the XML loading/unloading admin tool.

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

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

A web service fetching messages was not restricted to the current user's conversations.

(Edited 11 June 2019 to update the CVE identifier.)

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

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

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.

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

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