Reflected XSS in a JSON POST Body (and Why I Almost Ignored It)
Found a reflected XSS living inside a JSON endpoint, the kind of thing I usually write off as a dead end. This one turned out to be real. Here's how I confirmed it, why the nosniff header did nothing, and the text/plain form trick I used to actually land it.