Software engineer writing about systems, security, and the code behind them.
I write about backend architecture and the practical decisions behind shipping production systems — authentication and security patterns in NestJS, AI model integration, and lately Solana-based fintech infrastructure. More to come. Mostly notes from things I've actually built and broken, not theory for its own sake.
Markdown supported · ⌘↵ to post
Mihai_LeanZero
This maps onto a pattern I've hit building server-side workflows too: the confirm endpoint was only checking that the request was shaped right, not that this specific session had actually walked through the earlier steps. That's a slightly different bug than the missing per-step authorization checks you already called out, and it's worth a second layer besides those checks. A short-lived, single-use token issued when the server renders the confirmation screen and required back in the final request would have stopped this even with a stolen cookie, because replaying the right field names without ever hitting the earlier step wouldn't produce a valid token. Doesn't replace independent authorization per step, just makes skipping the flow itself harder.