Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-85333

Editing LTI tools exposes the sesskey in a read GET request

      ie editing an instance looks like:

      /mod/lti/typessettings.php?action=update&id=2160&sesskey=QH19TmDKbE&returnto=toolconfigure

      The first page should simply not require a sesskey at all, only the POST when saving it should.

      At a quick glance it looks like many of the LTI pages suffer from the same problems, eg from this page:

      /mod/lti/toolproxies.php

      when you click 'Configure a new external tool registration' you get the same issue:

      /mod/lti/registersettings.php?action=add&sesskey=QH19TmDKbE&tab=tool_proxy

            benjaminwalker Benjamin Walker
            brendanheywood Brendan Heywood
            Brendan Heywood Brendan Heywood
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 10 minutes
                10m

                  Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.