-
Sub-task
-
Resolution: Fixed
-
Minor
-
1.8.10, 1.9.6, 2.0
-
None
-
Any
-
MOODLE_18_STABLE, MOODLE_19_STABLE, MOODLE_20_STABLE
-
MOODLE_18_STABLE, MOODLE_19_STABLE, MOODLE_20_STABLE
-
Easy
The XMLDB Editor is missing sesskey protection (thanks Petr for spotting that). While it's difficult to perform any attack based on that (mainly because of the session-based nature of the whole editor), to be 100% sure and correct the sesskey thing must be applied to all "edit" actions in the editor.
Going to do it. Ciao