Session token sent in url


During the scan, Kayran managed to find that a Session token is being sent in the URL.
Sensitive information within URLs could be logged in various locations, including the user’s browser, the web server, and any (forward or reverse) proxy servers between the two endpoints.

This vulnerability could allow attackers to steal the Session token. That, will allow them to redirect users to malicious and external websites which could lead to creating a wide array of attack vectors.


CVSS Version 3.x – 5.3 Medium


Applications should use an alternative much safer mechanism for transferring session tokens. Mechanisms such as HTTP cookies or hidden fields in forms that are submitted using the POST method.


< Return to all Vulnerabilities

Red Team

You’ve probably heard that there are teams in the Cyber field called Red Team and Blue Team. Let’s talk about the red one, shall we?

Read More »


How to preform SQLI TO RCE? One of the most interesting and important things about any site is the database. So, it’s important to protect

Read More »

Browser Exploitation

We know that it’s possible to exploit weaknesses (or vulnerabilities) that exist in anything, from a certain code to the entire application, let’s talk about

Read More »