I'm willing to bet that this is due to some browser extension on the user's side messing with CORS headers. But too late, the outrage mob has already assembled.
That said its likely a bug and nothing nefarious. Not to diminish that this is a really severe issue that you should raise to customer support, who likely has ways of cancelling for you.