Almost every login page has one: /login?next=/account/settings . You sign in, the server reads next , and sends you back where you were. It's a small convenience, and it's one of the most common places a site ends up forwarding its users to a URL somebody else chose.
The bug itself is old and well understood. What keeps it alive is the check developers put in front of it. next.startswith("/") looks airtight. So does "the URL contains our domain". Both fail, and they fail for the same reason: your server-side code and the user's browser don't read URLs the same way.
This post covers where open redirects hide, why the usual checks miss, how to prove one without overclaiming, and a validator that holds up because it parses like the browser does. All examples use stand-in hosts ( app.example.com for the app, evil.example for "somewhere you don't control").β¦