FIND AND EXPLOIT COMMON WEB VULNERABILITIES
github: PAYLOAD ALL THE THINGS
Here is the high-level, simple breakdown of how these three vulnerabilities work:
SQL Injection (SQLi):
Occurs when an attacker types database commands into a standard input field (like a login box). The application mistakes this text for legitimate instructions, allowing the attacker to steal, alter, or delete private data directly from the database.
Cross-Site Scripting (XSS)
happens when an attacker injects malicious browser code (JavaScript) into a webpage. The website accidentally saves this code and displays it to other visitors, causing the malicious script to run in innocent users' browsers to steal passwords or session cookies.
Command Injection takes place when an attacker inputs operating system commands into an application. The app accidentally passes those instructions straight to the underlying server, giving the attacker direct control over the host machine just like a rogue administrator.
INSECURE FILE UPLOADING
Phase 1: Interception & Modification
In Burp Suite: You capture the file upload HTTP request using the Proxy, send it to Repeater, and manipulate the payload—such as changing the file extension (e.g., .jpg to .php) or tampering with the Content-Type header.
The Goal: To bypass weak client-side restrictions or superficial server-side validation filters.
Phase 2: Execution & Verification
In Burp Suite: You forward the edited request, analyze the server's response to locate the uploaded file's URL or path, and then access that path via the browser.
The Goal: To trigger the execution of the uploaded malicious script on the server, typically resulting in Remote Code Execution (RCE).
Sanitanization Defenses - es no php, can be avoided with the following extension renaming