Agility, Java programming, New technologies and more…
  • rss
  • Home
  • Management
  • Agile Programming
  • Technology
  • Linux
  • Event
  • Android app
  • Contact
  • About the author
  • English
  • Francais

Tips to make your WordPress website secure

Fabian Piau | Wednesday October 10th, 2018 - 06:43 PM
  • Print
  • Twitter
  • LinkedIn
  • Facebook
  • Pocket

 Version française disponible

Update
January, 14th, 2021 : Update security headers, replaced “Feature-policy” with “Permissions-policy”.

WordPress is one of the most popular CMS (Content Management System). That popularity also means that it is a target of choice for hackers.
In this article, I will give you some tips to keep your website secure and avoid being attacked.


1. Use latest versions

This is true for WordPress itself but also for all your extensions. There are new versions available regularly. If a plugin has not been updated for a while, it is probably not maintained anymore and you might need to remove or replace it. This is also applicable for your theme.
The version of PHP is also important, check with your hosting provider that you are running the latest version of PHP (7.X), especially the versions 5.X won’t be supported by the end of the year.
Also, note that the more extensions you have installed, the more risk you are taking, as your WordPress configuration will rely on more 3rd party code. You should only keep the plugins that you really need. If a plugin is disabled, don’t keep its source code and remove all its associated files.


2. Use secure login details

Never use the default admin user. If you do, disable this account and create your own account with a personalized username.
Choose a strong password. If several users are managing your website, make sure the permissions are valid and avoid giving the admin permission to everyone.


3. Scan your website

This is an easy and quick way to find vulnerabilities and see if one of your plugins is vulnerable or not. You can use these 2 online tools:

  • WordPress Security Scan (my favourite with a detailed report)
  • WPSec


4. Use .htaccess files to protect your directories

The .htaccess file is a server configuration file. It allows you to define rules for your server to follow.

For example, in /wp-content/uploads, I have created the following .htaccess:

# Deny access to everything by default
Order deny,allow
Deny from all

# Allow access to media files
<FilesMatch '\.(jpg|jpeg|png|gif|bmp|zip|rar|pdf)$'>
    Allow from all
</FilesMatch>

This config ensures only media files are accessible from the browser, any JavaScript, PHP files will be discarded. It is not 100% bulletproof as only the extension is checked, but it is better than nothing.

To avoid execution of malicious PHP in some folder (e.g. in /wp-includes), you can create another .htaccess file with the following content:

<Files *.php>
Order allow,deny
Deny from all
</Files>


5. Review file and directory permission

Make sure the critical files (wp-config.php, php.ini…) are not writable publicly, only readable. Only owners should be able to write.


6. Use security headers

You can check which security headers you currently use with this online tool.

At the root folder, update the .htaccess file and add:

# Extra Security Headers
<IfModule mod_headers.c>
	Header set Strict-Transport-Security 'max-age=31536000; includeSubDomains'
	Header set X-XSS-Protection '1; mode=block'
	Header set X-Frame-Options 'sameorigin'
	Header set X-Content-Type-Options 'nosniff'
	Header unset Server
	Header always unset X-Powered-By
	Header unset X-Powered-By
	Header unset X-CF-Powered-By
	Header unset X-Mod-Pagespeed
	Header unset X-Pingback
</IfModule>

In wp-config.php, add:

/** Extra Security */
header('X-Frame-Options: SAMEORIGIN');
header('X-XSS-Protection: 1; mode=block');
header('X-Content-Type-Options: nosniff');
header('Strict-Transport-Security:max-age=31536000; includeSubdomains; preload');
header('Referrer-Policy: no-referrer-when-downgrade');
header('Content-Security-Policy: upgrade-insecure-requests');
header('Permissions-Policy: autoplay=(), camera=(), encrypted-media=(), fullscreen=(), geolocation=(), microphone=(), midi=(), payment=()');
header_remove('X-Powered-By');
header_remove('Server');
header_remove('X-CF-Powered-By');
header_remove('X-Mod-Pagespeed');
header_remove('X-Pingback');
@ini_set('session.cookie_httponly', true);
@ini_set('session.cookie_secure', true);
@ini_set('session.use_only_cookies', true);


7. Do not expose too much information

At the root folder of your website, in php.ini, add the line:

expose_php = Off

Your current version of PHP will not be exposed.


8. Backup your website regularly

Last but not least! You don’t need a particular software or extra plugin to achieve this.

  • With your favourite FTP tool (e.g. Filezilla), save all the files available on your server.
  • For the database, use the available MySQL backup feature. Many hosting companies provide access to phpMyAdmin, an online tool.

I recommend doing a backup every month, and keep the history of the last 6 backups somewhere safe. Of course, it depends on the volume of articles you are writing and how critical is your data.


That’s it! If you have done all the above, your website should be more resilient to attacks. In the worst case, you should be able to recover easily.

Happy safe blogging!

Related posts

Maven siteMaven Site, one step further IT securitySome basic rules to prevent your accounts from getting hacked Apache CamelFirst steps with Apache Camel printerOptimize your website for print in 5 minutes
Comments
No Comments »
Categories
Technology
Tags
hacking, hacker, security, wordpress
Comments rss Comments rss

Some basic rules to prevent your accounts from getting hacked

Fabian Piau | Friday November 1st, 2013 - 10:15 AM
  • Print
  • Twitter
  • LinkedIn
  • Facebook
  • Pocket

 Version française disponible

Note
April 2014, the internet world discovers the wide “Heartbleed” security bug. Recommandation is to change all your passwords. Take advantage of Heartbleed by choosing better passwords :)

When we think of computer security, security software like antivirus, firewalls immediately come to mind. Actually, we forget that one of the root causes of hacking is… you!

The hacker

Prevention is better than cure.

You know that old saying, because it can apply to your computer habits as well.


A good security starts with a good password

  • Use a different password for each application you are using. At least, if someone finds out your Facebook password, he won’t be able to connect to your Twitter account.

  • Currently, many websites (even some famous ones) don’t encrypt passwords of their users. Who has not received an email including a password reminder?
    One might say: hooray, that’s great, I will be able to recover my password easily in case I forget it. Actually, it would be better to think: hum, if my email gets hacked, the hacker will get this password, especially it means that my password is somewhere in plain language in a database. It also means the administrator or other people can see it (and imagine if the website gets hacked).
    Unfortunately, the problem is not on your side, but again it is a really good reason to have different passwords.

  • Your password must be neither simple nor logical. A date of birth, the name of your pet or one of your children, a word taken from the dictionary… Avoid all of these! Mechanisms like brute force attack (i.e. trying all combinations to find out the password) will eventually find it in a short amount of time (hardware is very powerful now). Therefore, I advise you to choose a password not too short and containing a mix of uppercase, lowercase letters and numbers. Of course, a complex password is great but if you have to write it down on a post’it to remember it, that’s not the right solution either. You have to strike a happy medium.

  • When it is possible, use advanced authentication strategies. For example, it can be a confirmation code sent on your phone. This kind of service is usually proposed by largest software companies such as Google or Facebook.


A good security also requires common sense

  • Avoid to connect to public Wi-Fi networks and other free hotspots. This is especially true when you connect to unsecured services. Insecure means that data exchanges are not encrypted. You can easily identify secure services when they are using the ‘https’ prefix in the URL (the ‘s’ is important), hopefully the most popular applications support it.
    Why? A bad guy can listen to the network and collect all the exchanged data (thanks to a sniffer), the bunch of data is difficult to read at first sight, but an expert will be able to isolate any useful information. In the case you are searching for kitten videos on YouTube, you will not care a lot, but if you are logging in to an application through an unsecured form, I guess it will be more annoying…

  • When you download your software, always take a look at the download URL.
    For instance, if you want to download the latest version of iTunes, go systematically on the Apple website, avoid generic websites such as downloadfreesoftwares.com (I will not be surprised if this website exists). First, use publisher websites. Ultimately, use famous and trusted download websites.

  • Same thing when you are using an online service, make sure it can be trusted before you register and provide your personal information.

  • Pay attention to your emails. Especially when you receive strange ones that could not be identified as spam by your email software.
    Just yesterday, I received an email from the French tax department to inform me about a refund of 178.20 euros due to a mistake. The email was so real (no misspelling) that I thought it was good news. When I clicked on the link, I realized there was something wrong. It was not the usual website URL of the French government, and above all I needed to enter my credit card information. This is clearly a phishing attempt: a fake page with a classic form that reproduced exactly the official website (design interface, header, footer and so on). It’s really easy to fall into the trap.

  • One last tip, update your software and applications when new updates are available. It can be your browser, its plugins, any installed software… or even your blog’s engine (if you have one, I use WordPress that is updated several times a year).
    Every day, security vulnerabilities are discovered and corrected. A security glitch is usually (at least when it is a big one) published in the press, it becomes a door left open for hackers. I do not want to scare you, but remember it!


Every day if you follow these advices and are vigilant, you should avoid any kind of virtual trouble! At least, you cannot say that nobody warned you!

I realize I have denigrated cats a little bit in this article, I hope they will forgive me…

Cat - What do you want?

Related posts

wordpress-hackerTips to make your WordPress website secure EclipseChanging the Eclipse splash screen in few seconds updapyUpdapy, the applications update center for Windows seo performance websiteThe best free and online tools for testing and optimizing an application or website
Comments
No Comments »
Categories
Technology
Tags
account, flaw, phishing, hacking, hacker, security, spam
Comments rss Comments rss
Page 1 of 11
Download CarmaBlog App

RSS feeds

  • RSS feed RSS - Posts
  • RSS feed RSS - Comments

Most viewed posts

  • Changing the language in Firefox - 116,375 views
  • Using Google Forms / Drive / Docs to create an online survey - 64,403 views
  • FAQ – Online survey with Google Forms / Drive / Docs - 56,247 views
  • Customizing Gnome 3 (Shell) - 30,809 views
  • The meaning of URL, URI, URN - 18,407 views
  • Java EE & CDI vs. Spring - 15,986 views
  • Open Street Map, better map than Google Maps? - 15,800 views
  • Comparing NoSQL: Couchbase & MongoDB - 14,693 views
  • API, REST, JSON, XML, HTTP, URI… What language do you speak? - 13,730 views
  • First steps with Apache Camel - 13,597 views

Recent Comments

  • Fabian Piau on FAQ – Online survey with Google Forms / Drive / DocsOui, dans Google Forms, vous pouvez empêcher les p…
  • BENECH Fabien on FAQ – Online survey with Google Forms / Drive / DocsBonjour, J'ai crée 1 questionnaire via Forms,…
  • SANKARA TIDIANE on Free online MongoDB trainingJ'aimerai suivre
  • Pauline on FAQ – Online survey with Google Forms / Drive / DocsMerci Fabian, mais le but étant que nos clients pu…
  • Fabian Piau on FAQ – Online survey with Google Forms / Drive / DocsProbablement mais ces options sont en général paya…

Recent posts

  • How to write a blog post? At least my way! - 2 years and 5 months ago
  • Bot Attacks: You are not alone… - 4 years and 1 month ago
  • Flagger – Monitor your Canary deployments with Grafana - 4 years and 10 months ago
  • Flagger – Canary deployments on Kubernetes - 5 years and 2 days ago
  • Flagger – Get Started with Istio and Kubernetes - 5 years and 2 weeks ago
  • Expedia CoderDojo in London - 5 years and 9 months ago
  • Volunteering at Devoxx4Kids - 6 years and 2 weeks ago
  • A Java 11 migration successful story - 6 years and 4 months ago
  • Tips to make your WordPress website secure - 6 years and 7 months ago
  • Devoxx UK 2018 – Day 2 - 6 years and 11 months ago
  • Devoxx UK 2018 – Day 1 - 7 years and 12 hours ago
  • Wise, Revolut and Monzo, a small revolution for travelers and expats - 7 years and 3 months ago
  • Autocomplete for Git - 8 years and 1 day ago
  • Swagger, the automated API documentation - 8 years and 2 months ago
  • Microservices architecture – Best practices - 8 years and 7 months ago
Buy me a coffee

Language

  • Français
  • English

Follow me!

Follow me on Linkedin
Follow me on Twitter
Follow me on Stackoverflow
Follow me on Github
Follow me on Rss
Link to my Contact

Email subscription

Enter your email address to receive notifications of new posts.

Tags

.net agile agility android bash best practices blog cache cloud computing conference continuous integration css developer devoxx docker eclipse extreme programming firefox flagger google helm hibernate istio java job jug kubernetes london mobile computing overview performance plugin programmer script security sharing society spring tdd test tool ubuntu windows wordpress

Links

  • Blog Ippon Technologies
  • Blog Publicis Sapient
  • Blog Zenika
  • Classpert
  • CommitStrip
  • Coursera
  • Le Touilleur Express
  • Les Cast Codeurs Podcast
  • OCTO talks !
  • The Twelve-Factor App

Categories

  • Event (15)
  • Linux (3)
  • Management (8)
  • Agile programming (29)
  • Technology (45)

Archives

  • December 2022 (1)
  • April 2021 (1)
  • June 2020 (1)
  • May 2020 (2)
  • July 2019 (1)
  • May 2019 (1)
  • December 2018 (1)
  • October 2018 (1)
  • June 2018 (1)
  • May 2018 (1)
  • January 2018 (1)
  • May 2017 (1)
  • March 2017 (1)
  • October 2016 (1)
  • April 2016 (2)
  • March 2016 (1)
  • November 2015 (1)
  • May 2015 (1)
  • February 2015 (1)
  • December 2014 (1)
  • November 2014 (1)
  • September 2014 (2)
  • August 2014 (1)
  • July 2014 (2)
  • June 2014 (1)
  • April 2014 (1)
  • March 2014 (1)
  • February 2014 (2)
  • January 2014 (1)
  • December 2013 (1)
  • November 2013 (1)
  • October 2013 (3)
  • September 2013 (5)
  • July 2013 (1)
  • June 2013 (1)
  • May 2013 (1)
  • April 2013 (1)
  • March 2013 (2)
  • February 2013 (1)
  • January 2013 (2)
  • December 2012 (2)
  • October 2012 (1)
  • September 2012 (1)
  • July 2012 (1)
  • May 2012 (1)
  • April 2012 (1)
  • March 2012 (1)
  • February 2012 (1)
  • January 2012 (2)
  • December 2011 (1)
  • November 2011 (2)
  • October 2011 (2)
  • September 2011 (1)
  • July 2011 (1)
  • June 2011 (2)
  • April 2011 (1)
  • March 2011 (1)
  • February 2011 (1)
  • January 2011 (2)
  • November 2010 (2)
  • September 2010 (1)
  • August 2010 (1)
  • July 2010 (1)
  • June 2010 (1)
  • May 2010 (1)
  • April 2010 (1)
  • March 2010 (1)
  • February 2010 (1)
  • December 2009 (1)
  • November 2009 (1)
  • October 2009 (2)
  • September 2009 (2)
  • August 2009 (3)
  • July 2009 (1)
  • June 2009 (2)
Follow me on Twitter
Follow me on Linkedin
Follow me on Stackoverflow
Follow me on Rss
Link to my Contact
Follow me on Github
 
Fabian Piau | © 2009 - 2025
All Rights Reserved | Top ↑