File upload security risks in PHP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a common security risk when allowing file uploads in PHP?

Uploading malicious files that can execute harmful code on the server, such as PHP scripts disguised as images.

beginner

Why should you validate the file type during upload?

To ensure only allowed file types are accepted, preventing attackers from uploading dangerous files like executable scripts.

intermediate

What is the risk of not limiting file size in uploads?

Attackers can upload very large files to exhaust server storage or cause denial of service by overloading resources.

intermediate

How can storing uploaded files outside the web root improve security?

It prevents direct access to uploaded files via URL, reducing the chance of executing malicious files on the server.

beginner

What is the purpose of renaming uploaded files?

Renaming files avoids overwriting existing files and prevents attackers from guessing file locations or executing scripts by name.

Which of the following is a key risk when accepting file uploads in PHP?

A Uploading a file smaller than 1KB

B Uploading a text file with no content

C Uploading a PHP script disguised as an image

D Uploading a file with a .txt extension

Malicious PHP scripts disguised as images can run harmful code on the server if not properly checked.

What is a good practice to prevent execution of uploaded files?

A Allow all file types

B Disable file size limits

C Use the original file name

D Store files outside the web root directory

Storing files outside the web root prevents direct access and execution via URL.

Why should you check the MIME type of an uploaded file?

A To verify the file is of an allowed type

B To increase upload speed

C To reduce file size

D To rename the file automatically

Checking MIME type helps confirm the file content matches allowed types, improving security.

What can happen if you do not limit the size of uploaded files?

A Server storage can be exhausted

B Files will upload faster

C Files will be automatically deleted

D Users can upload only images

Large files can fill server storage and cause denial of service.

Renaming uploaded files helps to:

A Make files larger

B Prevent overwriting and guessing file paths

C Allow execution of scripts

D Disable file uploads

Renaming files avoids conflicts and hides original file names from attackers.

Explain the main security risks involved with file uploads in PHP and how to mitigate them.

Think about how attackers might use file uploads to harm the server.

Describe best practices to securely handle file uploads in a PHP application.

Focus on steps that reduce risk of malicious files and server overload.

Practice

1. Which of the following is the most important reason to validate file types during a PHP file upload?

easy

A. To make the upload process faster

B. To allow uploading any file without restrictions

C. To reduce server storage space

D. To prevent users from uploading harmful scripts disguised as files

Solution

1. Step 1: Understand file upload risks

   Malicious users can upload harmful scripts if file types are not checked.

2. Step 2: Importance of validation

   Validating file types helps block dangerous files and protects the server.

3. Final Answer:

   To prevent users from uploading harmful scripts disguised as files -> Option D

4. Quick Check:

   File type validation = prevent harmful uploads [OK]

Hint: Always check file types to block dangerous uploads [OK]

Common Mistakes:

• Ignoring file type validation
• Assuming all files are safe
• Only checking file extensions without content

2. Which PHP function is commonly used to check the MIME type of an uploaded file for security?

easy

A. mime_content_type()

B. is_uploaded_file()

C. file_get_contents()

D. move_uploaded_file()

Solution

1. Step 1: Identify function purpose

   mime_content_type() returns the MIME type of a file, useful for validation.

2. Step 2: Compare with other functions

   move_uploaded_file() moves files, file_get_contents() reads content, is_uploaded_file() checks upload status.

3. Final Answer:

   mime_content_type() -> Option A

4. Quick Check:

   Check MIME type = mime_content_type() [OK]

Hint: Use mime_content_type() to verify file type safely [OK]

Common Mistakes:

• Using move_uploaded_file() to check file type
• Confusing file_get_contents() with type checking
• Not verifying MIME type at all

3. What will be the output of this PHP code snippet if a user uploads a file named image.jpg with size 5MB, but the allowed max size is 2MB?

$maxSize = 2 * 1024 * 1024; // 2MB
if ($_FILES['file']['size'] > $maxSize) {
    echo 'File too large';
} else {
    echo 'Upload successful';
}

medium

A. File too large

B. Upload successful

C. No output

D. Syntax error

Solution

1. Step 1: Understand size check logic

   The code compares uploaded file size to maxSize (2MB).

2. Step 2: Compare actual file size

   Uploaded file is 5MB, which is greater than 2MB, so condition is true.

3. Final Answer:

   File too large -> Option A

4. Quick Check:

   5MB > 2MB triggers 'File too large' [OK]

Hint: Compare file size with max allowed size [OK]

Common Mistakes:

• Confusing bytes and megabytes
• Not multiplying correctly for max size
• Ignoring file size check

4. Identify the security issue in this PHP file upload code snippet:

if (move_uploaded_file($_FILES['file']['tmp_name'], 'uploads/' . $_FILES['file']['name'])) {
    echo 'Upload successful';
} else {
    echo 'Upload failed';
}

medium

A. Using original filename without sanitization

B. All of the above

C. Missing check if file is uploaded via HTTP POST

D. No file size check before upload

Solution

1. Step 1: Check file size validation

   Code does not check file size before moving the file.

2. Step 2: Check filename handling

   Using original filename directly risks overwriting and security issues.

3. Step 3: Check upload method validation

   Missing is_uploaded_file() check to confirm HTTP POST upload.

4. Final Answer:

   All of the above -> Option B

5. Quick Check:

   Missing size, sanitization, and upload checks [OK]

Hint: Check size, sanitize name, verify upload method [OK]

Common Mistakes:

• Ignoring filename sanitization
• Not verifying upload method
• Skipping file size validation

5. You want to securely handle file uploads in PHP by allowing only PNG images under 1MB, renaming files to a unique name, and preventing script execution. Which combination of steps is best?

hard

A. Check file size, move file with original name, allow all image types

B. Only check file extension, rename file, save in uploads folder

C. Check MIME type with mime_content_type(), limit size, rename with uniqid(), save outside web root

D. Skip validation, rename file, save in web root

Solution

1. Step 1: Validate file type and size

   Use mime_content_type() to confirm PNG and check size under 1MB.

2. Step 2: Rename file and secure storage

   Rename with uniqid() to avoid conflicts and save outside web root to prevent script execution.

3. Final Answer:

   Check MIME type with mime_content_type(), limit size, rename with uniqid(), save outside web root -> Option C

4. Quick Check:

   Validate type & size + rename + secure storage [OK]

Hint: Validate type/size, rename uniquely, store securely [OK]

Common Mistakes:

• Relying only on file extension
• Saving files in web root without restrictions
• Not renaming files uniquely