This application is vulnerable to password reset poisoning via dangling markup.

This application is vulnerable to password reset poisoning. The user carlos will carelessly click on any links in emails that he receives.

This app is vulnerable to routing-based SSRF via the Host header. Although the front-end server may initially appear to perform robust validation of the Host header, it makes assumptions about all requests on a connection based on the first request it receives.

This application makes an assumption about the privilege level of the user based on the HTTP Host header.

This application has a logic flaw in its purchasing workflow.

This application is vulnerable to routing-based SSRF due to its flawed parsing of the request's intended host. This can be exploited to access an insecure intranet admin panel located at an internal IP address.

This application is vulnerable to web cache poisoning due to discrepancies in how the cache and the back-end application handle ambiguous requests. An unsuspecting user regularly visits the site's home page.

This application makes flawed assumptions about the sequence of events in the login process.

This application makes a flawed assumption about the user's privilege level based on their input. As a result, it is possible to exploit the logic of its account management features to gain access to arbitrary users' accounts.

This application makes a flawed assumption about the user's privilege level based on their input. As a result, it is possible to exploit the logic of its account management features to gain access to arbitrary users' accounts.