As you can see, the POST to the script simply returns "403 forbidden":
The script itself is not "forbidden", as you can see when accessed directly with normal GET.
The above is basically the clear indicator that it's a firewall response. I see the same script works fine when doing normal save, without customizing the sort order. So it means your firewall is explicitly triggering for the POST data that is related to image sort index. I can't really know from here what specific rule it is, or even why it's triggering at all, but below is POST data from custom sorting:
This is something you need to resolve with your hosting. Ultimately, your firewall doesn't really need to be enabled from the /panel/* url, because everything that goes on there requires login anyway (but your firewall doesn't know that).