SQL injection prevention in Wordpress - Step-by-Step Execution

Concept Flow - SQL injection prevention

User Input Received

↓

Sanitize Input

↓

Prepare SQL Statement

↓

Bind Parameters

↓

Execute Query

↓

Return Safe Results

↓

END

The flow shows how user input is cleaned, safely added to SQL commands, and executed to avoid injection.

Execution Sample

Wordpress

<?php
$user_id = $_GET['id'];
$stmt = $wpdb->prepare("SELECT * FROM wp_users WHERE ID = %d", $user_id);
$results = $wpdb->get_results($stmt);
?>

This code safely queries the database for a user by ID using prepared statements to prevent SQL injection.

Execution Table

Step	Action	Input/Variable	Result/Output	Notes
1	Receive user input	$_GET['id'] = '5 OR 1=1'	Raw input: '5 OR 1=1'	User tries to inject SQL code
2	Prepare SQL statement	SQL: "SELECT * FROM wp_users WHERE ID = %d", param: '5 OR 1=1'	Prepared SQL with placeholder	Input not directly inserted
3	Bind parameter	Bind '5 OR 1=1' as integer	Parameter converted to integer 5	Non-numeric part ignored, safe binding
4	Execute query	Final SQL: "SELECT * FROM wp_users WHERE ID = 5"	Query runs safely	Injection attempt neutralized
5	Return results	Query result for user ID 5	User data for ID 5	Safe data returned
6	End	No further action	Process complete	SQL injection prevented

💡 Execution stops after query safely runs with sanitized input, preventing injection.

Variable Tracker

Variable	Start	After Step 1	After Step 3	Final
$user_id	undefined	'5 OR 1=1'	5	5
$stmt	undefined	undefined	"SELECT * FROM wp_users WHERE ID = %d"	"SELECT * FROM wp_users WHERE ID = 5"
$results	undefined	undefined	undefined	User data for ID 5

Key Moments - 2 Insights

Why does binding the parameter as an integer prevent SQL injection?

Because the binding converts the input to a safe type (integer), ignoring malicious parts like 'OR 1=1', as shown in step 3 of the execution_table.

What happens if we insert user input directly into the SQL without prepare()?

The raw input would be part of the SQL string, allowing injection. The execution_table step 2 shows how prepare() avoids this by using placeholders.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of $user_id after binding in step 3?

A '5 OR 1=1'

B 5

C NULL

D 1=1

💡 Hint

Check the 'Bind parameter' row in execution_table where input is converted to integer.

At which step does the SQL injection attempt get neutralized?

A Step 3

B Step 1

C Step 2

D Step 5

💡 Hint

Look for where the parameter is safely bound and converted in execution_table.

If we skip using $wpdb->prepare(), what risk increases?

A Faster query execution

B More accurate results

C SQL injection vulnerability

D No risk at all

💡 Hint

Refer to key_moments explaining the importance of prepare() in preventing injection.

Concept Snapshot

SQL injection prevention in WordPress:
- Always use $wpdb->prepare() for queries with user input.
- Use placeholders (%d, %s) to safely bind parameters.
- Binding converts inputs to safe types, blocking injection.
- Never insert raw user input directly into SQL.
- This keeps your database safe and your site secure.

Full Transcript

This visual execution shows how WordPress prevents SQL injection by using prepared statements. First, user input is received, which might contain malicious code. Then, the input is not directly added to the SQL query. Instead, $wpdb->prepare() creates a safe SQL statement with placeholders. The user input is bound as a parameter, converting it to a safe type like integer. This stops any injection attempts. The query runs safely and returns correct results. Key moments highlight why binding is crucial and the risks of skipping prepare(). The quiz tests understanding of these steps and variable changes.