You've proven the bug. You have the request that shows it, the response that confirms it, and the browser's network log that ties it together. The easiest way to hand all of that to a triager, a developer or a vendor's support desk is a HAR file: one click in DevTools, one attachment.
That file is also a copy of your session. Every cookie, every Authorization header, every token the app returned in a response body is in there, in plain JSON. Whoever reads the attachment, or whoever later gets into the system it was uploaded to, can try to replay it.
This isn't a hypothetical. In October 2023, Okta reported unauthorized access to its support system, where customers upload HAR files for troubleshooting. Okta noted that HAR files can contain cookies and session tokens, revoked the tokens embedded in them, and recommended sanitizing credentials before sharing.…