{"id":2395,"date":"2017-09-01T14:50:47","date_gmt":"2017-09-01T18:50:47","guid":{"rendered":"https:\/\/www.knownhost.com\/blog\/?p=2395"},"modified":"2026-01-21T13:24:25","modified_gmt":"2026-01-21T18:24:25","slug":"10-mistakes-people-make-first-start-wordpress","status":"publish","type":"post","link":"https:\/\/www.knownhost.com\/blog\/10-mistakes-people-make-first-start-wordpress\/","title":{"rendered":"10 Mistakes People Make When They First Start With WordPress"},"content":{"rendered":"

The incredible popularity of WordPress gives hackers an incentive to go after it. Once they find a way in, they can replicate the attack across thousands or even millions of sites. One of the most prominent ways that the CMS has been attacked most recently is through a content-injection weakness that was identified early this year and patched by WordPress 4.7.2. Regardless of the patch, 1.5 million sites were defaced by February 10, according to Threatpost<\/em><\/a>. It is one of the worst points of WordPress compromise to ever develop, according to WP security plugin maker WordFence. The problem (an issue with a REST API endpoint that led to unauthenticated privilege escalation) was patched by WordPress 4.7.2 on January the 26th<\/sup> \u2013 although news of the patch didn\u2019t emerge right away. One of the core developers noted that the CMS organization waited to let people know about the vulnerability until people were able to make the update and clear themselves from potential exploit.<\/p>\n

Since hacking is devastating to businesses (with one report indicating that 3 in 5<\/a> hacked businesses go bankrupt within six months), it is important to focus on that particular element. However, we will not neglect various other ways that companies can, well, screw up with WordPress when they\u2019re getting started. Let\u2019s look at some of the most frequently occurring mistakes so that you can avoid them.<\/p>\n