OWASP: Information Exposure Through Query Strings in URL

OWASP: Information Exposure Through Query Strings in URL Vulnerability Overview Information exposure occurs when sensitive data (such as usernames, passwords, tokens, database details, and other potential sensitive information) is passed as parameters in a URL. Using HTTPS alone does not mitigate this vulnerability. Attackers can retrieve this sensitive data via the URL query string. Impact Scope Prevalence: Common Detectability: Difficult Technical Impact: Moderate Exposure Vectors: Sensitive data may be exposed in the following locations: Referer Header Web Logs Shared Systems Browser History Browser Cache Risk: Attackers may leverage leaked data (such as OTPs or passwords) to gain unauthorized access. Remediation Avoid Passing Sensitive Data in URLs: Do not place passwords, OTPs (One-Time Passwords), or other sensitive credentials in the URL query string. Use Secure Transmission Methods: For sensitive data, use the POST method or other secure transmission mechanisms instead of GET requests. POC / Exploit Code Examples Example 1 (General Exposure): Note: Parameters , , and will be exposed in HTTP or HTTPS requests. Example 2 (Real-World Case - OTP Exposure): Note: This URL exposes the OTP token and personally identifiable information (email) in browser history, server logs, and third-party monitoring tools.

Goal Reached Thanks to every supporter — we hit 100%!

OWASP: Information Exposure Through Query Strings in URL