{"id":28069,"date":"2016-06-21T16:17:22","date_gmt":"2016-06-21T13:17:22","guid":{"rendered":"http:\/\/blog.superhosting.bg\/en\/?p=28069"},"modified":"2022-04-02T09:55:38","modified_gmt":"2022-04-02T06:55:38","slug":"cms-installations-risk","status":"publish","type":"post","link":"https:\/\/blog.superhosting.bg\/en\/cms-installations-risk.html","title":{"rendered":"The Importance of Finishing CMS Installation in your Hosting Account"},"content":{"rendered":"

You’ve got a brand new super hosting account<\/a> so you can’t wait to create an amazing web project. Just when the installation package is uploaded and you are about to install the CMS, your phone suddenly starts ringing. It is your boss calling and you need to run an errand ASAP! Well, it is inevitable \u2013 the installation should wait for a better time.<\/p>\n

But what can happen until that “better time” comes? At first glance, there is nothing to worry about. But let’s have a closer look.<\/p>\n

What is required for installing a CMS in your hosting account?<\/h4>\n

Contemporary content management systems usually consist of two parts \u2013 files and databases. To start the installation, you first need to upload the files in your account. Then create a database and a user. Run the CMS installation script by accessing the URL in a web browser and follow the steps to finish up the installation. On the different steps you usually enter the website’s name, admin data, a password, database to be used, etc.<\/p>\n

You’ve reached the step for running the installation script, but the information is still not entered, hence the installation is not completed. Here is how this step looks in the most popular content management system \u2013 WordPress:<\/p>\n

\"The<\/p>\n

However, the URL (which is usually your domain name) can be accessed by anyone. While you are not working on your website, other users can reach it. But, believe it or not, they might not have good intentions.<\/p>\n

Malicious activities can occur when other people finish the CMS installation on your behalf. The database should not necessarily originate from the same account where your website is hosted. Most often the website’s files and the database are hosted in the same account. But this is not the only available option. It is possible for the database to be on a separate server.<\/p>\n

\"The<\/p>\n

That’s exactly what “bad guys” use to their advantage. They create a database and a user on another server which they have access to. Afterwards they finish up your installation and connect your website to their database.<\/p>\n

This provides them with: access to the website’s administration.<\/h4>\n

Anyone who has access to the website’s administration is enabled to install plugins, themes or add-ons. What is worse, compromised files might be also uploaded to your website without your consent. Usually this is the only malicious activity performed. In this way changes might stay unnoticed.<\/p>\n

And you will not figure out what have happened to your website. Why?<\/h4>\n

Because after all actions are performed to your installation, the “bad guys” usually delete the configuration file. In this way they terminate any connection with the database so that the CMS installation looks just like you left it \u2013 waiting for you to finish it.<\/p>\n

Tip from the support: <\/strong> Do not leave an uninstalled CMS in your hosting account. If you miss the chance to install the CMS right after uploading it, you would better delete it. When you are able to finish your installation, just upload the package again.<\/div>\n

You can install the most widely-used CMSs trough Softaculous<\/a>.<\/p>\n

Keep your account well-ordered. If there is a CMS which you have only tested but you do not intend to use, we recommend that you delete it as soon as possible.<\/p>\n","protected":false},"excerpt":{"rendered":"

Do not leave an uninstalled CMS in your hosting account. While you are not working on your website, other users can reach it.<\/p>\n","protected":false},"author":7,"featured_media":53841,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[118],"tags":[129],"class_list":{"0":"post-28069","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-superhosting-tips-of-support-en","8":"tag-security-campaign"},"aioseo_notices":[],"modified_by":"\u041c\u0430\u0434\u043b\u0435\u043d\u0430 \u041c\u0435\u0442\u043e\u0434\u0438\u0435\u0432\u0430","post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/blog.superhosting.bg\/en\/wp-json\/wp\/v2\/posts\/28069","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.superhosting.bg\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.superhosting.bg\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.superhosting.bg\/en\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.superhosting.bg\/en\/wp-json\/wp\/v2\/comments?post=28069"}],"version-history":[{"count":4,"href":"https:\/\/blog.superhosting.bg\/en\/wp-json\/wp\/v2\/posts\/28069\/revisions"}],"predecessor-version":[{"id":64918,"href":"https:\/\/blog.superhosting.bg\/en\/wp-json\/wp\/v2\/posts\/28069\/revisions\/64918"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.superhosting.bg\/en\/wp-json\/wp\/v2\/media\/53841"}],"wp:attachment":[{"href":"https:\/\/blog.superhosting.bg\/en\/wp-json\/wp\/v2\/media?parent=28069"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.superhosting.bg\/en\/wp-json\/wp\/v2\/categories?post=28069"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.superhosting.bg\/en\/wp-json\/wp\/v2\/tags?post=28069"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}