Sanitization methods in Express - Step-by-Step Execution

Concept Flow - Sanitization methods

Receive user input

↓

Apply sanitization method

↓

Clean input: remove/escape harmful parts

↓

Use sanitized input safely

↓

Send response or store data

User input is received, cleaned using sanitization methods to remove harmful content, then safely used in the app.

Execution Sample

Express

const { body, validationResult } = require('express-validator');

app.post('/submit', [
  body('username').trim().escape(),
], (req, res) => {
  const errors = validationResult(req);
  if (!errors.isEmpty()) return res.status(400).json({ errors: errors.array() });
  res.send(`Hello, ${req.body.username}`);
});

This code trims and escapes the 'username' input to sanitize it before using it.

Execution Table

Step	Action	Input Value	Sanitization Method	Output Value	Result
1	Receive input	<script>alert(1)</script>	trim	<script>alert(1)</script>	Whitespace removed
2	Apply escape	<script>alert(1)</script>	escape	&lt;script&gt;alert(1)&lt;/script&gt;	HTML tags escaped
3	Validation check	&lt;script&gt;alert(1)&lt;/script&gt;	validationResult	No errors	Input is safe to use
4	Use sanitized input	&lt;script&gt;alert(1)&lt;/script&gt;	send response	Hello, &lt;script&gt;alert(1)&lt;/script&gt;	Safe output sent
5	End	-	-	-	Request handled safely

💡 Input sanitized and validated, safe to use in response

Variable Tracker

Variable	Start	After trim	After escape	Final
req.body.username	<script>alert(1)</script>	<script>alert(1)</script>	&lt;script&gt;alert(1)&lt;/script&gt;	&lt;script&gt;alert(1)&lt;/script&gt;

Key Moments - 2 Insights

Why do we use both trim() and escape() on the input?

trim() removes extra spaces which can cause unexpected issues, while escape() converts harmful characters like < and > to safe codes, preventing code injection. See execution_table steps 1 and 2.

What happens if validationResult finds errors?

The code stops processing and returns a 400 error with details. This prevents unsafe input from being used. This is shown in execution_table step 3.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of req.body.username after the escape method?

A <script>alert(1)</script>

B &lt;script&gt;alert(1)&lt;/script&gt;

C >tpircs/<)1(trela>tpircs<

D alert(1)

💡 Hint

Check the 'After escape' column in variable_tracker and step 2 in execution_table.

At which step does the code confirm the input is safe to use?

A Step 3

B Step 1

C Step 4

D Step 2

💡 Hint

Look for validationResult check in execution_table step 3.

If we remove the escape() method, what risk increases?

A Input will have extra spaces

B Validation will fail

C Input might contain harmful HTML or scripts

D Input will be empty

💡 Hint

Escape method converts harmful characters; see execution_table step 2.

Concept Snapshot

Sanitization methods clean user input to keep apps safe.
Use trim() to remove spaces.
Use escape() to convert harmful characters.
Validate input before use.
Always sanitize before storing or displaying input.

Full Transcript

In Express, sanitization methods help clean user input to prevent harmful data from causing problems. First, input is trimmed to remove extra spaces. Then, escape converts characters like < and > into safe codes so scripts can't run. Validation checks if input is okay. If all is good, the sanitized input is used safely in the app. This process protects your app from attacks like cross-site scripting. The example code shows trimming and escaping a username before sending it back in a response. The execution table traces each step, showing how the input changes and when it is safe. Remember, always sanitize and validate input to keep your app secure.