So this exploit is really the confluence of failing to follow 2 standard security practices, as well as another unfortunate configuration quirk:
- Failing to set SameSite=lax on their session cookie attribute - Not using a CSRF token to authenticate on unsafe HTTP actions - Not checking the content-type of API requests (though I'm not sure to what extent this is considered bad practice)