Start learning with our library of video tutorials taught by experts. Get started
Viewed by members. in countries. members currently watching.
This course explains how to secure self-hosted WordPress sites, including site configuration, code modification, and the use of free plug-ins. Beginning with the basics of site security, author Jeff Starr explains how to harden a WordPress site by configuring authentication keys, setting proper file permissions, and removing version numbers. The course shows how to implement a firewall, prevent automated spam, and control proxy access, and concludes with a series of advanced tips and site security best practices.
A big part of good security is keeping sensitive information away from the bad guys. WordPress has one particular weakness in this department: it likes to display its version number in the source code of your web pages and feeds. The WordPress version number is displayed in the source code of your web pages, and it looks like this here. The version number is also displayed in your RSS feeds, and the version number is also displayed elsewhere and in other feeds. This information seems harmless but may enable attackers to target security holes in specific versions of WordPress.
In this screencast, we'll see how to better protect your site by preventing WordPress from announcing its version number. Let's peek behind the scenes at the HTML markup for the homepage of this WordPress demo site. Notice here in the head section that WordPress is providing the version number of this installation right here. This information is used by hackers and automated scripts to attack specific versions of the software. We can also see it in the source code of the various feeds that WordPress generates.
Returning to the homepage, click on the RSS link, and we see right here the version number of WordPress, displayed in the source code. Of course, if you're always running the latest most up-to-date version of WordPress, there is no reason not to show this information, but people can't always upgrade the minute a new version of WordPress is available. So it's smart to play it safe and just prevent the information from being displayed on any occasion. Let's return to the FTP editor.
So to stop WordPress from displaying its version number, let's navigate to our active theme, which for the demo site is the default TwentyTen theme. Then we open our theme's functions.php file, as we have done here. We want to add the following lines of code to the bottom of this file. Included with the screencast is this code here, which you may copy and then paste after all other code in the functions.php file.
Now let's save the file and upload it to the server. Here in the source code, we can see that the version number is no longer available, not being displayed, and that's a good thing, but that's not the only place, as we have seen. So let's check the RSS feed. As we can see, our code snippet in the functions.php file has prevented WordPress from displaying its version number in the RSS feed as well. In fact, with that code in place, WordPress will not display the version number anywhere that is easily accessible by hackers and people who want to exploit your site.
In this screencast a simple code snippet in the functions.php file stops WordPress from displaying sensitive information in feeds, posts, pages, and everywhere else. By simply disabling the version generator, we add yet another layer of security to our WordPress-powered site.
There are currently no FAQs about WordPress 3: Developing Secure Sites.
Access exercise files from a button right under the course name.
Search within course videos and transcripts, and jump right to the results.
Remove icons showing you already watched videos if you want to start over.
Make the video wide, narrow, full-screen, or pop the player out of the page into its own window.
Click on text in the transcript to jump to that spot in the video. As the video plays, the relevant spot in the transcript will be highlighted.