Input validation vs sanitization in PHP - When to Use Which

The Big Idea

What if a tiny unchecked input could break your whole website or steal data?

The Scenario

Imagine you run a website where users type their names and emails. Without checking or cleaning this input, bad data or harmful code can sneak in.

The Problem

Manually checking every input is slow and easy to forget. Mistakes let wrong or dangerous data cause errors or security holes.

The Solution

Input validation checks if data looks right before using it. Sanitization cleans data to remove harmful parts. Together, they keep your site safe and working well.

Before vs After

✗ Before

$name = $_POST['name'];
$email = $_POST['email'];
// no checks or cleaning

✓ After

$name = filter_var($_POST['name'], FILTER_SANITIZE_SPECIAL_CHARS);
$email = filter_var($_POST['email'], FILTER_VALIDATE_EMAIL);

What It Enables

It lets you trust user input so your app stays safe and runs smoothly.

Real Life Example

When signing up for a newsletter, validation ensures the email looks real, and sanitization removes any strange code someone might try to sneak in.

Key Takeaways

Validation checks if input is correct.

Sanitization cleans input to remove bad parts.

Both protect your app from errors and attacks.

Practice

1. What is the main purpose of input validation in PHP?

easy

A. To remove unwanted characters from the input

B. To store input data in a database

C. To check if the input data meets expected rules or format

D. To encrypt the input data for security

Solution

1. Step 1: Understand input validation meaning

   Input validation means checking if the data entered by the user follows the expected format or rules, like checking if an email looks like an email.

2. Step 2: Compare with other options

   Removing unwanted characters is sanitization, storing data is unrelated, and encrypting is a different security step.

3. Final Answer:

   To check if the input data meets expected rules or format -> Option C

4. Quick Check:

   Validation = Check input format [OK]

Hint: Validation means checking input correctness, not cleaning it [OK]

Common Mistakes:

• Confusing validation with sanitization
• Thinking validation changes the input
• Assuming validation stores or encrypts data

2. Which PHP function is used primarily for sanitizing an email input?

easy

A. filter_var($email, FILTER_VALIDATE_EMAIL)

B. trim($email)

C. htmlspecialchars($email)

D. filter_var($email, FILTER_SANITIZE_EMAIL)

Solution

1. Step 1: Identify sanitization function for email

   FILTER_SANITIZE_EMAIL removes illegal characters from an email string, cleaning it.

2. Step 2: Differentiate from validation and other functions

   FILTER_VALIDATE_EMAIL checks if email is valid (validation). htmlspecialchars escapes HTML, trim removes spaces.

3. Final Answer:

   filter_var($email, FILTER_SANITIZE_EMAIL) -> Option D

4. Quick Check:

   Sanitize email = FILTER_SANITIZE_EMAIL [OK]

Hint: Sanitize email uses FILTER_SANITIZE_EMAIL, not VALIDATE [OK]

Common Mistakes:

• Using FILTER_VALIDATE_EMAIL for sanitization
• Confusing htmlspecialchars with sanitization
• Ignoring trimming spaces as sanitization

3. What will be the output of this PHP code?

$input = "[e-mail]";
$sanitized = filter_var($input, FILTER_SANITIZE_EMAIL);
echo $sanitized;

medium

A. alert('Hi');[e-mail]

B. [e-mail]

C. <script>alert('Hi');</script>[e-mail]

D. Syntax error

Solution

1. Step 1: Understand FILTER_SANITIZE_EMAIL effect

   This filter removes illegal characters but keeps some like apostrophes and semicolons, so the alert part remains partially.

2. Step 2: Analyze input and output

   The <script> tags are removed, but alert('Hi'); remains before the email, so output is alert('Hi');[e-mail].

3. Final Answer:

   alert('Hi');[e-mail] -> Option A

4. Quick Check:

   Sanitize email removes tags but keeps some chars [OK]

Hint: Sanitize email removes tags but may keep some symbols [OK]

Common Mistakes:

• Expecting full removal of script content
• Confusing sanitization with escaping HTML
• Assuming syntax error from special chars

4. Identify the error in this PHP code snippet for validating an integer input:

$age = "25";
if (filter_var($age, FILTER_SANITIZE_NUMBER_INT)) {
  echo "Valid age";
} else {
  echo "Invalid age";
}

medium

A. Using FILTER_SANITIZE_NUMBER_INT instead of FILTER_VALIDATE_INT

B. Missing semicolon after echo statements

C. Incorrect variable name in filter_var

D. No error, code is correct

Solution

1. Step 1: Check filter used for validation

   FILTER_SANITIZE_NUMBER_INT cleans input but does not validate if it's a proper integer.

2. Step 2: Correct filter for validation

   FILTER_VALIDATE_INT should be used to check if input is a valid integer.

3. Final Answer:

   Using FILTER_SANITIZE_NUMBER_INT instead of FILTER_VALIDATE_INT -> Option A

4. Quick Check:

   Validation needs FILTER_VALIDATE_INT, not sanitize [OK]

Hint: Validation uses FILTER_VALIDATE_INT, not sanitize filters [OK]

Common Mistakes:

• Confusing sanitize and validate filters
• Ignoring filter_var second argument importance
• Assuming sanitize also validates

5. You want to accept a username input that must be alphanumeric and between 5 to 10 characters. Which approach correctly combines validation and sanitization in PHP?

hard

A. Validate with FILTER_VALIDATE_REGEXP for pattern, then sanitize with FILTER_SANITIZE_STRING

B. Sanitize with FILTER_SANITIZE_STRING, then validate length and ctype_alnum

C. Only sanitize with FILTER_SANITIZE_STRING, no validation needed

D. Only validate length with strlen, ignore sanitization

Solution

1. Step 1: Understand validation and sanitization order

   First sanitize the input to remove unwanted characters using FILTER_SANITIZE_STRING.

2. Step 2: Validate length and alphanumeric

   Then validate the length with strlen and check if the string is alphanumeric using ctype_alnum.

3. Final Answer:

   Sanitize with FILTER_SANITIZE_STRING, then validate length and ctype_alnum -> Option B

4. Quick Check:

   Sanitize first, then validate pattern and length [OK]

Hint: Sanitize first, then validate length and alphanumeric [OK]

Common Mistakes:

• Validating before sanitizing
• Skipping sanitization and trusting validation only
• Ignoring length check in validation