File permission hardening in Wordpress - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main goal of file permission hardening in WordPress?

To restrict access to files and folders so only authorized users and processes can read, write, or execute them, improving security.

beginner

Which file permission setting is recommended for WordPress files?

Files should generally have permissions set to 644, meaning the owner can read/write, and others can only read.

beginner

What permission setting is recommended for WordPress directories?

Directories should usually be set to 755, allowing the owner to read/write/execute and others to read/execute only.

intermediate

Why should the wp-config.php file have stricter permissions?

Because wp-config.php contains sensitive information like database credentials, it should be set to 600 or 640 to limit access.

beginner

What is the risk of setting WordPress files or folders to 777 permissions?

Setting permissions to 777 allows anyone to read, write, and execute, which can lead to unauthorized changes and security breaches.

What permission should you set for WordPress directories to keep them secure?

A 755

B 777

C 644

D 600

755 allows the owner full access and others read and execute, which is secure for directories.

Which file permission is safest for wp-config.php?

A 777

B 644

C 600

D 755

600 restricts access to only the owner, protecting sensitive data in wp-config.php.

Why should you avoid 777 permissions on WordPress files?

A It allows anyone to modify files

B It makes files read-only

C It hides files from users

D It encrypts the files

777 lets anyone read, write, and execute files, risking unauthorized changes.

What does the permission 644 mean for a file?

A Everyone can read/write

B Owner can read/write; group and others can read

C Only owner can read/write

D Owner can execute only

644 means owner has read/write, others have read-only access.

Which WordPress folder should never be writable by the public?

A /wp-content/uploads

B /wp-includes

C /wp-content/plugins

D /wp-admin

/wp-admin contains core admin files and should be protected from public write access.

Explain why setting correct file and directory permissions is important in WordPress security.

Think about who can read, write, or execute files and why that matters.

Describe the risks of using overly permissive settings like 777 on WordPress files and folders.

Consider what happens if everyone can change your website files.

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