Welcome to FastCart!

Featured Products

Gadget Pro X

The ultimate tech companion.

$299.99

SmartWatch Elite

Track your fitness in style.

$149.50

AeroBuds Max

Immersive audio experience.

$99.00

MechKey Pro

Precision gaming keyboard.

$119.99

SoundBlast Mini

Big sound, small package.

$75.00

RealityView VR

Next-gen virtual reality.

$499.00

SQL Injection Demonstration

Username

Password

Try: admin' OR '1'='1 for username

Behind the Scenes: The Vulnerability

1. The Vulnerable Server-Side Code:


// (Simplified server-side code example, e.g., Node.js with SQL)
const username = req.body.username; // User input directly
const password = req.body.password;

// VULNERABLE LINE: Concatenating input directly into the SQL string
const sqlQuery = "SELECT * FROM users WHERE username = '" + username + "' AND password = '" + password + "';";

// In a real app, this query would be executed against the database
// e.g., database.query(sqlQuery);

Problem: The red line shows user input (`username`) being directly inserted into the SQL query string. This is called **string concatenation** and is the root cause of SQL Injection.

2. How 'admin' OR '1'='1' Exploits It:


-- If user enters: admin' OR '1'='1
-- The database receives this query:

SELECT * FROM users WHERE username = 'admin' OR '1'='1' AND password = 'any_password';

The `' OR '1'='1'` part closes the username field's quote, then adds an `OR` condition that is always true, bypassing the password check.
Result: The query becomes `SELECT * FROM users WHERE username = 'admin' OR '1'='1'`, logging you in without a valid password.

3. The Secure Way: Prepared Statements


// (Secure server-side code example)
const username = req.body.username;
const password = req.body.password;

// SECURE WAY: Using placeholders (?) and parameters
const sqlQuery = "SELECT * FROM users WHERE username = ? AND password = ?;";

// Database driver handles parameter binding safely.
// Input is treated as data, never as executable code.
database.execute(sqlQuery, [username, password]);

With Prepared Statements, placeholders (`?`) are used in the query. The user input is passed separately as parameters. The database understands these parameters are *values*, not part of the SQL command, preventing injection.

Understanding & Preventing SQL Injection

What is SQL Injection?

SQL Injection (SQLi) is a web security vulnerability that allows an attacker to interfere with the queries that an application makes to its database. It allows the attacker to view data that they are not normally able to retrieve, or even modify or delete data, and in some cases, issue commands to the operating system.

In the demonstration, the attacker exploited a vulnerable login form by injecting a malicious string into the username field. This manipulated the database query, allowing them to bypass authentication without needing a valid password.

How to Protect Against SQL Injection

Prepared Statements (Parameterized Queries):

This is the most effective defense. Instead of directly embedding user input into SQL queries, prepared statements treat user input as data, not as executable code. The database engine then handles the input safely.

// Example (conceptual, not runnable JS)
// const username = userInput;
// const password = userPass;
// const query = "SELECT * FROM vendors WHERE username = ? AND password = ?";
// database.execute(query, [username, password]); // Parameters are sent separately

Input Validation:
Validate and sanitize all user-supplied input on both the client-side (for user experience) and, more importantly, the server-side. This includes checking data types, lengths, formats, and escaping special characters.
Principle of Least Privilege:
Configure database users with the minimum necessary permissions. If an attacker gains access, their capabilities will be limited, reducing the potential damage.
Web Application Firewalls (WAFs):
A WAF can help filter and block malicious traffic, including common SQL injection patterns, before they reach your application.
Error Handling:
Avoid displaying verbose database error messages to users, as these can provide valuable information to an attacker. Log errors internally instead.
Regular Security Audits & Penetration Testing:
Periodically review your code and conduct penetration tests to identify and fix vulnerabilities before they can be exploited by malicious actors.

Welcome to FastCart!

Featured Products

Gadget Pro X

SmartWatch Elite

AeroBuds Max

MechKey Pro

SoundBlast Mini

RealityView VR

SQL Injection Demonstration

Behind the Scenes: The Vulnerability

1. The Vulnerable Server-Side Code:

2. How 'admin' OR '1'='1' Exploits It:

3. The Secure Way: Prepared Statements

Admin Dashboard Access Granted!

Customer Data

Order History

Product Inventory

Sales Reports

Understanding & Preventing SQL Injection

What is SQL Injection?

How to Protect Against SQL Injection

Welcome to FastCart!

Featured Products

Gadget Pro X

SmartWatch Elite

AeroBuds Max

MechKey Pro

SoundBlast Mini

RealityView VR

SQL Injection Demonstration

FastCart Login

Behind the Scenes: The Vulnerability

1. The Vulnerable Server-Side Code:

2. How 'admin' OR '1'='1' Exploits It:

3. The Secure Way: Prepared Statements

Admin Dashboard Access Granted!

Customer Data

Order History

Product Inventory

Sales Reports

Understanding & Preventing SQL Injection

What is SQL Injection?

How to Protect Against SQL Injection