How do I secure Zen Cart against hacking?

SSL Security

Without applying extra efforts to your connection on the internet you are wandering around an unsecured environment. Before you make administrative modifications to secure Zen Cart and its database, you need to equip yourself with secure ways to make these modifications. Otherwise if someone is watching/listing to the information you transmit, it might not be long before your private business information becomes public. The bare minimum you should have is access to shared SSL services from your hosting company.

The preferred would be to have a dedicated SSL certificate for your store, as it is more professional in appearance than the use of a shared certificate. There will be an expense incurred to obtain a dedicated SSL certificate and dedicated IP address in your hosting account.

Delete the /zc_install folder

Once installation is complete, delete the /zc_install folder from the server. Don't simply rename the folder, as this leaves you vulnerable if someone were to discover this renamed folder.

Rename your /admin folder

It is recommended for additional security that you rename your admin directory after installation. This way, it will be significantly harder for hackers to find your admin area or attempt any attack on breaking into it.

(Before making the following changes, make sure to have a current backup of your files and your database.)

[1] Open your admin/includes/configure.php, using a simple text editor like notepad. Change all instances of admin to your chosen new admin folder-name. For maximum security, you may want to consider that new folder name should include numbers and a combination of upper and lower case letters. The longer you make this folder's name the more secure it will be. Make sure you leave all the / intact.

[2] Change this section:

define('DIR_WS_ADMIN', '/admin/');
define('DIR_WS_CATALOG', '/');
define('DIR_WS_HTTPS_ADMIN', '/admin/');
define('DIR_WS_HTTPS_CATALOG', '/');

And this section:

define('DIR_FS_ADMIN', '/home/mystore.com/www/public/admin/');
define('DIR_FS_CATALOG', '/home/mystore.com/www/public/');

[3] Find your Zen Cart /admin/ directory, using your FTP software or your cPanel File Manager. Rename the directory to match the settings you just made above.

[4] To login to your admin system you will now have to visit a new URL that matches the new name used above. Use of SSL is highly recommended to protect you and your customers' information. To protect the new admin folder name from packet sniffers, use HTTPS when accessing your admin area.

[5] You should also protect your admin area by using an .htaccess file similar to the one shown below, and placing it into /admin/includes. This should already exist in Zen Cart versions 1.2.7 and greater.

Set configure.php files read-only

It's important that you CHMOD (set permissions) on the two configure.php files as read-only. Typically this means setting them to 644, or in some cases 444.

The configure.php files are located here:

includes/configure.php
admin/includes/configure.php

After setting the permissions on these files, you must verify the correct setting by entering the store and seeing if there is a warning message on the top of the screen.

Warning: I am able to write to the configuration file:...

In this case you will need to use the "File Manager" supplied with your webhosting account.
If you're using a Windows server, simply set the file as Read-Only for Everyone and especially the IUSR_xxxxx (Internet Guest Account) user if running IIS, or the System account or apache user if running Apache.

Delete any unused Admin accounts

Admin > Tools > Admin Settings

In your Admin area, open the Tools menu, and choose Admin Settings. Check for any unused Admin accounts, and delete them. Especially the Demo account, if it exists.

Admin Password Security

It is wise to use complicated passwords so that a would-be hacker can't easily guess them.

You can change your Admin password in Admin > Tools > Admin Settings, and click on the Reset Password button, or click on the icon that looks like a recycle symbol.

We recommend that you use passwords that are at least eight characters long. Making them alpha-numeric (including letters, numbers, upper-and-lower-case, etc) helps too. If you are going to use normal words it is a good idea to join together two normal words that don't normally go together.

After you have finished editing your define pages (Admin > Tools > Define Pages Editor), you should protect them:

[1] Download a copy of them to your PC using your FTP software. They are located in the /includes/languages/english/html_includes area.

[2] Make them CHMOD 644 (or "read-only" for Windows hosts). See notes above on CHMOD. /includes/languages/english/html_includes - and all files/folders underneath

If you make them read-only, then a would-be hacker cannot edit them if they gain access to your system, unless they can get permissions to change the read-only status, which is more complicated.

Once you set them read-only, then you'll have to go and set them read-write before making additional changes using the define-pages editor.

Use .htaccess files to protect against unwanted snooping

In several folders, there are .htaccess files to prevent users from being able to browse through the files on your site unless they know exact filenames. Some also prevent access to any .PHP scripts, since it's expected that all PHP files in those folders will be accessed by other PHP files, and not by a browser directly. This is good for security. If you delete these files, you run the risk of leaving yourself open to people snooping around.

There are also some blank index.html files in several folders. These files are there to protect you in case your FTP software won't upload .htaccess files, or your server won't accept them. These only prevent directory browsing, and do not stop execution of .PHP files. It's a good alternative, although using .htaccess files in all of these folders is the better choice, for servers that accept them.

Suggested content for .htaccess files in folders where there is an index.html file but not yet an .htaccess file would be something like the following (depends on your server configuration):

#.htaccess to prevent unauthorized directory browsing or access to .php files
IndexIgnore */*

Order Deny,Allow
Deny from all

#add the following to protect against people discovering what version your spiders.txt file is
Order Deny,Allow
Deny from all

If your webhost configuration doesn't allow you to create/use your own .htaccess files, sometimes they provide an interface in your hosting admin control panel where you can set the desired .htaccess settings.

It is recommended that you work with your host to configure these settings if this is the method they require. You need to choose, and use, the appropriate method for your server. As mentioned above, it's best to work with your web hosting company to select and implement the best method for your specific server. We can't tell you what to use for your specific server, but we offer these guidelines as a starting point.

Disable "Allow Guest To Tell A Friend" feature

You may wish to go to Admin > Configuration > Email Options > Allow Guest To Tell A Friend and set the option to false. This will prevent non-logged-in customers from using your server to send unwanted email messages.

Protect your "images" and other folders

During initial installation, you are advised to set your images folder to read/write, so that you can use the Admin interface to upload product/category images without having to use FTP for each one. Similar recommendations are made to other files for various reasons. However, leaving the images (or any other) folder in read/write mode means that hackers might be able to put malicious files in this (or other) folder(s) and thus create access points from which to attempt nasty exploits.

Thus, once your site is built and your images have been created/loaded, you should drop the security down from read/write to read. ie: change from CHMOD 777 down to 644 for files and 755 for folders.

File/Folder permissions settings

On Linux/Unix hosts, generally, permission-setting recommendations for basic security are:

• Folders/Directories: 755
• Files: 644

Folder Purposes The folders for which installation suggests read-write access for setup are these. If your site supports .htaccess protection, then you should use it for these folders.

cache folder

/cache - This is used to cache session and database information.

The BEST security protection for this is to move it to a folder "above" the public_html/htdocs/www area, so that it's not accessible via a browser.

(Requires changes to DIR_FS_SQL_CACHE setting in configure.php files as well as Admin > Configuration > Sessions > Session Directory.

images folder

/images - See other suggestions earlier.

includes/languages/english/html_includes

/includes/languages/english/html_includes - See other suggestions earlier.

media folder

/media - This is only suggested read-write for the sake of being able to upload music-product media files via the admin. Could be done by FTP as an alternative.

pub folder

/pub - This is used on Linux/Unix hosts to have downloadable products made available to customers via a secure delivery method which doesn't disclose the 'real' location of files/data on your server (so that people can't share a URL and have their friends steal downloads from your site)

admin/backups

/admin/backups - This is used by automated backup routines to store database backups. Optional.

admin/images/graphs

/admin/images/graphs - This is used by the Admin > Tools > Banner Manager for updating/displaying bar graphs related to banner usage. If not writable, feature is ignored.

Things to Check Up on Regularly

[1] Be sure you've done all the steps listed in this document.

[2] Make recent backups of your website files and database.

[3] Backup the database over a secure connection (SSL).

[4] Backup the website files over a secure connection FTP over SSL/TLS.

[5] Store the backed up database and website files into an encrypted file.

[6] Check your server's error log regularly for odd or suspicious activity.

[7] Look for any links that went to a page that isn't in your site.

[8] Look for links that have http after the index.php.

[9] Check your website files regularly to be sure nothing's been added or altered.