Brightloom is a client portal used by a design agency. Comment threads are shared with the client, and staff read them in the same page you do.
You have pasted an image tag into a comment. It appears on the thread as text — you can see the angle brackets, so something escaped it on the way out.
The composer has a Rich text toggle. You have never switched it on.
One change to this request triggers the vulnerability. The challenge is to use your security intuition to work out what to change. Find the value the server shouldn’t trust, change it, and send it. The response tells you whether you were right.
Hint. Make this comment run in another reader’s browser.
“Content is escaped, so the output is safe.”
Sanitise after rendering rather than instead of it: run every renderer’s output through one allowlist-based cleaner on the way out, so no path reaches the page unfiltered. Turn off raw HTML in the markdown renderer, and take the choice of renderer from the author’s saved preference rather than from the request that carries the content.
Anywhere a request selects how its own content will be displayed: rich-text and markdown flags, content_type or mime fields on a note, an email that can be sent as HTML or text, a description rendered differently in preview and in print, a legacy renderer kept for old records. The tell is more than one output path for one field, with the escaping in only some of them.
One Request Away is a daily series of challenges. They’re like code review, but for HTTP requests: in each one you’re one request away from triggering a vulnerability, and your goal is to identify what you need to change.