File permission hardening in Wordpress - Step-by-Step Execution

Concept Flow - File permission hardening

Identify WordPress files and folders

↓

Check current permissions

↓

Apply recommended permissions

↓

Verify permissions applied

↓

Test site functionality

↓

Adjust if needed or finish

This flow shows checking and setting secure file permissions on WordPress files and folders step-by-step.

Execution Sample

Wordpress

find /var/www/html -type d -exec chmod 755 {} \;
find /var/www/html -type f -exec chmod 644 {} \;
chmod 600 /var/www/html/wp-config.php

This code sets directories to 755, files to 644, and wp-config.php to 600 for security.

Execution Table

Step	Action	Target	Permission Before	Permission After	Result
1	Check directory permissions	/var/www/html/wp-content	777	755	Directories set to 755
2	Check file permissions	/var/www/html/index.php	666	644	Files set to 644
3	Secure wp-config.php	/var/www/html/wp-config.php	644	600	Config file restricted
4	Verify permissions	/var/www/html/wp-content	755	755	Permissions confirmed
5	Verify permissions	/var/www/html/wp-config.php	600	600	Permissions confirmed
6	Test site	WordPress site	N/A	N/A	Site loads correctly
7	End	N/A	N/A	N/A	File permission hardening complete

💡 All files and folders have secure permissions and site functionality verified.

Variable Tracker

Target	Initial Permission	After Step 1	After Step 2	After Step 3	Final
/var/www/html/wp-content (directories)	777	755	755	755	755
/var/www/html/index.php (files)	666	666	644	644	644
/var/www/html/wp-config.php	644	644	644	600	600

Key Moments - 3 Insights

Why do directories get permission 755 but files get 644?

Directories need execute permission (x) to allow entering them, so 755 (rwxr-xr-x) is used. Files don't need execute permission unless they are scripts, so 644 (rw-r--r--) is safer. See execution_table steps 1 and 2.

Why is wp-config.php set to 600 instead of 644 like other files?

wp-config.php contains sensitive info like database passwords, so it needs stricter permissions (read/write only by owner). This is shown in execution_table step 3.

What if the site breaks after changing permissions?

Check if permissions are too restrictive, especially on wp-content or wp-config.php. The last step in execution_table shows testing site functionality to catch this.

Visual Quiz - 3 Questions

Look at the execution_table, what permission does /var/www/html/index.php have after step 2?

A 644

B 666

C 755

D 600

💡 Hint

Check the 'Permission After' column for step 2 in execution_table.

At which step is wp-config.php permission changed to 600?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look for the action 'Secure wp-config.php' in execution_table.

If directories were set to 700 instead of 755, what might happen?

A Files become executable

B No change, 700 is same as 755

C Site might break because web server can't access directories

D Files get deleted automatically

💡 Hint

Consider the need for execute permission on directories from key_moments and execution_table step 1.

Concept Snapshot

File permission hardening in WordPress:
- Directories: 755 (rwxr-xr-x) to allow access
- Files: 644 (rw-r--r--) for safety
- wp-config.php: 600 (rw-------) for sensitive data
- Verify permissions and test site after changes
- Prevents unauthorized file access and changes

Full Transcript

File permission hardening in WordPress means setting the right permissions on files and folders to keep the site safe. Directories get permission 755 so the server can enter them. Files get 644 so they can be read but not changed by others. The wp-config.php file is extra protected with 600 because it holds passwords. The process is: check current permissions, apply recommended ones, verify them, and test the site to make sure it still works. This stops hackers from changing or reading files they shouldn't. If permissions are too strict, the site might break, so testing is important.

Practice

1. What is the main purpose of file permission hardening in WordPress?

easy

A. To add more plugins automatically

B. To speed up the website loading time

C. To protect the site from unauthorized changes

D. To change the website theme

Solution

1. Step 1: Understand file permission hardening

   File permission hardening means setting rules on who can read, write, or execute files to keep the site safe.

2. Step 2: Identify the main goal

   The goal is to stop unauthorized users from changing files, which protects the site from harm.

3. Final Answer:

   To protect the site from unauthorized changes -> Option C

4. Quick Check:

   File permission hardening = Protect site [OK]

Hint: Think security first: permissions stop unwanted changes [OK]

Common Mistakes:

• Confusing permission hardening with performance tuning
• Thinking it adds features like plugins or themes
• Believing it changes website design

2. Which chmod command correctly sets safe permissions for WordPress files?

easy

A. chmod 777 wp-config.php

B. chmod 644 index.php

C. chmod 000 wp-content

D. chmod 222 wp-admin

Solution

1. Step 1: Recall safe file permissions

   Files should be readable and writable by the owner, readable by others, usually 644.

2. Step 2: Check each option

   chmod 644 index.php sets 644 on a file, which is safe. Others either give too many rights or none.

3. Final Answer:

   chmod 644 index.php -> Option B

4. Quick Check:

   Safe file permission = 644 [OK]

Hint: Files usually get 644 permission, not 777 or 000 [OK]

Common Mistakes:

• Using 777 which is too open and unsafe
• Setting 000 which blocks all access
• Confusing file and folder permissions

3. Given the command chmod 755 wp-content, what is the effect on the wp-content folder?

medium

A. Owner can read, write, execute; others can read and execute only

B. Everyone can read, write, and execute the folder

C. No one has any permissions on the folder

D. Only the owner can read, write, and execute; others have no access

Solution

1. Step 1: Understand permission digits 755

   7 means owner can read(4), write(2), execute(1) = 7; 5 means others can read(4) and execute(1) = 5.

2. Step 2: Apply to wp-content folder

   Owner has full rights; others can read and execute but not write.

3. Final Answer:

   Owner can read, write, execute; others can read and execute only -> Option A

4. Quick Check:

   755 = Owner full, others read+execute [OK]

Hint: 755 means owner full, others read+execute only [OK]

Common Mistakes:

• Thinking 755 allows others to write
• Confusing execute permission with write
• Assuming no access for others

4. You set chmod 777 wp-config.php to fix a permission error, but the site becomes vulnerable. What is the problem?

medium

A. 777 allows anyone to read, write, and execute the file, risking security

B. 777 blocks all access to the file

C. 777 only allows the owner to access the file

D. 777 is the recommended permission for wp-config.php

Solution

1. Step 1: Understand what 777 permission means

   It gives read, write, and execute rights to everyone, including strangers.

2. Step 2: Assess security risk for wp-config.php

   This file holds sensitive info; open permissions let attackers change or read it.

3. Final Answer:

   777 allows anyone to read, write, and execute the file, risking security -> Option A

4. Quick Check:

   777 = Full access for all = Risk [OK]

Hint: Never use 777 on sensitive files like wp-config.php [OK]

Common Mistakes:

• Thinking 777 restricts access
• Believing 777 is safe for config files
• Confusing execute with write permission

5. To secure wp-config.php, which permission setting is best to prevent unauthorized reading but allow WordPress to function?

hard

A. chmod 644 wp-config.php

B. chmod 777 wp-config.php

C. chmod 000 wp-config.php

D. chmod 400 wp-config.php

Solution

1. Step 1: Understand wp-config.php security needs

   This file contains database passwords and keys, so it must be protected from others.

2. Step 2: Evaluate permission options

   400 means only owner can read; WordPress runs as owner, so it works. 644 allows others to read, 777 is too open, 000 blocks all access.

3. Final Answer:

   chmod 400 wp-config.php -> Option D

4. Quick Check:

   400 = Owner read only = Secure [OK]

Hint: Use 400 to lock wp-config.php to owner read only [OK]

Common Mistakes:

• Using 644 which lets others read sensitive info
• Using 777 which is insecure
• Using 000 which breaks WordPress access