wordpress-logo

Again with the “WordPress Isn’t Secure” Meme

As I was going about my morning reading, I came across an article with this dire headline: “The Perils of Using WordPress as a Hotel Website Content Management System.”  Of course, being a professional who spends much of his time working on WordPress, my interest was piqued.  From the article:

WordPress technology is ill-fitted to power hotel websites’ content management systems and is only adequate as a blogging technology.

Hmmm…that’s a pretty serious allegation.  So I read on.  The crux of his argument was that a WordPress system can be hacked using the technique described in the post contained in this article. So where is the fatal flaw?  Apparently if a user creates an insecure password, the system can be breached by blunt force.

Blunt force.  Right.  So if you were to ignore WordPress’ own warnings that your password was not strong, you might be hackable. This is not a system problem, it is a user problem.  It is in fact a problem inherent in computing in general and in any system which uses passwords.

Read on further and you’ll find the co-writers of this article have designed their own hotel content management system.  I’m going to guess that they don’t use passwords though, since those would be insecure.  But I will venture a guess without looking at their system:  it is neither open source,  nor are there millions of users who are trained and ready to work in the system.

I could continue ripping their post apart, but on further reading, it is an obvious attempt to get some Google juice for their site. They are simply not worth it.  If you have a hotel and want a simple, easy to use, and effective hotel website, drop me a line and I’ll get you set up for a fraction of what they’d charge you.  In the long run, you’ll be better off.

 

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>