Content Management Systems (CMS) are some of the most common targets of hacking on the Internet today.
In fact, a study conducted by WP White Security found that 73% of all WordPress installations contained known vulnerabilities that would have quickly and easily been found through the utilization of automated tools.
It’s these types of security holes that have resulted in cyber criminals hacking into over 170,000 back in 2012 alone – a number that is probably even higher by now.
CMS platforms are appealing targets to hackers for a wide variety of reasons, mainly the number of weak entry points – such as the numerous plugins available for CMS like WordPress.
Many people assume that, because CMS like WordPress and Drupal are highly popular and recognized names, there must be some form of protection. They can’t just leave all of their users vulnerable, right?
Think again.
CMS are inherently open to attack because of the fact their foundation is an open source framework. These types of shared development environments have myriad benefits, but they also come with just as many issues.
Because of the popularity of the top CMS available out there, the security holes within these systems are actively being identified and targeted, both by the good guys (security research teams) and the bad guys (cyber criminals).
Once these holes have been found, they turn that particular CMS into treasure troves of data for cyber criminals, even to the point of creating an entry point for automated attacks on a massive scale.
To add salt to the wound, there are users who use the same passwords for all of their accounts, or even just use weak passwords. These leave their admin accounts open to attacks, even if they aren’t aware of it. This can result in their websites being injected with all sorts of malware and escalating the issue beyond the point of control.
These issues can even result in the websites becoming blacklisted by Google and other search engines, which adversely affects their business or brand as a whole.
There are numerous things users can do to protect their CMS against vulnerabilities and fortify their systems from attack.
These include:
A vast amount of people know how to access CMS administrator backend, especially when it comes to popular sites like WordPress.
Make sure yours is secure with a strong password to make this process harder for hackers and other cyber criminals. Additionally, you’re going to want to hash the password(s) you use by implementing a slow hashing algorithm.
BONUS: Block the IP for at least one minute after x amount of password authentication failures. Three is the recommended amount of attempts before IP blocking.
Setting up a firewall will not only further secure your CMS, but it will also help you keep an eye on suspicious activity and track them by providing a related IP address for the source of that activity.
Once you’ve detected and found suspicious activity, you can then blacklist the IP the firewall provided.
This is one of the most essential aspects of CMS security, and is actually just an overall good habit to have.
Have a backup system in place that will make it possible to recover your website in the event something happens. Always make sure your backups are updated as much as possible to avoid any security vulnerabilities or further problems down the road.
BONUS: Make sure your CMS and any extensions it may have are updated. These upgrades should be double-checked to ensure they are fully compatible with your system before you allow or make them. Of course, you’re always going to want to backup your CMS before conducting these updates.
An SQL-injection is a cyber attack that embeds malicious code within your CMS and its backend database. Once it’s in there, that malicious code then creates database query results and / or actions that you definitely do not want executed.
There are several types of SQL-injections, and they enable the cyber criminal to do a whole variety of things. These include:
Editing, deleting, reading, or adding to the content of your CMS
Accessing and reading source code from the files on the CMS server
Write files to the server
While it is true that any one of those things relies heavily upon the capabilities of the cyber criminal, any SQL-injection can still lead to you losing control of your database and web server.
In order to prevent this from happening, use prepared statements, as these separate the structure and data. This allows the SQL server to interpret them without being open and vulnerable to a hacker that is trying to alter the structure of the SQL query for their own malicious purposes.
An SSL certificate (secure sockets layer) is the standard security technology that is used to produce an encrypted link that goes between the web server and the browser. It is this link that will ensure that the data that goes between the server and the browser will stay private and secure.
Adding an SSL certificate to your domain will not only add an additional layer of security to your CMS, but will also help with SEO because it tends to get your website ranked higher in search engines.
Website security is one of those things that can truly be considered a “Catch-22” type of situation.
The more cyber criminals are out there trying to gain access into people’s CMS, the more security researchers crack down on it and come with new methods of protection. The greater the security becomes, the harder the cyber criminals will work to gain access – and they do like challenges.
It’s really an ongoing battle that is seemingly without end.
But, where does that leave you and your CMS?
It’s hard to say for sure where your CMS lies within the cyber criminal-infested waters, but there are things you can do to ensure your CMS is as secure as you can possibly make it. These five methods of security will help reduce threats to your CMS and help keep your data out of jeopardy.