{"id":61,"date":"2018-03-13T00:50:01","date_gmt":"2018-03-13T00:50:01","guid":{"rendered":"https:\/\/meetanshi.com\/blog\/2018\/03\/13\/install-magento-supee-6788-with-or-without-ssh\/"},"modified":"2025-10-03T13:15:01","modified_gmt":"2025-10-03T07:45:01","slug":"install-magento-supee-6788-with-or-without-ssh","status":"publish","type":"post","link":"https:\/\/meetanshi.com\/blog\/install-magento-supee-6788-with-or-without-ssh\/","title":{"rendered":"How to Install Magento SUPEE 6788 with or without SSH"},"content":{"rendered":"\n

Securing the stores against any potential attacks or threats is a must factor for any E-commerce store. To serve this purpose, Magento releases Security Patches frequently. With the Security Patches correctly installed in Magento stores, the store owners increase the security and hence provide safe transaction experience to their customers!<\/p>\n\n\n\n

Magento released Security Patch SUPEE 6788<\/strong><\/em><\/a> on Oct 27, 2015, to ensure protection against threats such as remote code execution, information leaks, and cross-site scripting.<\/p>\n\n\n\n

With nearing of Magento 1 end of life, it is strongly recommended to migrate to the latest Magento 2.4.8<\/a>  rather than installing Magento SUPEE-6788<\/strong><\/em>.<\/p>\n\n\n\n

Installing Magento SUPEE 6788<\/h2>\n\n\n\n

One of the below methods is to be followed to install Magento SUPEE 6788.<\/p>\n\n\n\n

Method 1: Install Magento SUPEE 6788 using SSH<\/h3>\n\n\n\n

Contact your hosting provider if you don\u2019t know how to set up SSH. Download Magento SUPEE 6788<\/em> Patches files for your Magento Version from here<\/a>.<\/p>\n\n\n\n

Upload the patch into your Magento root directory and run the appropriate SSH command:<\/p>\n\n\n\n

For .sh file extension:<\/strong><\/p>\n\n\n\n

sh patch_file_name.sh<\/code><\/pre>\n\n\n\n
Example:<\/p>\n\n\n\n
sh PATCH_SUPEE-6788_CE_v1.9.3.2-1.9.3.7_v1-2018-02-23-06-01-40.sh<\/code><\/pre>\n\n\n\n
For .patch file extension:<\/strong><\/p>\n\n\n\n
patch \u2014p0 < patch_file_name.patch<\/code><\/pre>\n\n\n\n
Note:<\/strong> Once executed the command, refresh the cache in the Admin under \u201cSystem > Cache Management\u201d so that the changes can be reflected. We strongly recommend that you test all patches in a test environment before taking them live.<\/p>\n\n\n\n
Method 2: Install Magento SUPEE 6788 with PrePatched Files<\/h3>\n\n\n\n
Download the zip file for your Magento Version for the patch installation. You can also download these Pre Patched files from GitHub<\/a>. After downloading the files, just upload it to your Magento root folder.<\/p>\n\n\n\n
Magento Version<\/th>SUPEE 6788<\/th><\/tr><\/thead>
Magento 1.9.2.1<\/td>CE-1.9.2.1<\/a><\/td><\/tr>
Magento 1.9.2.0<\/td>CE-1.9.2.0<\/a><\/td><\/tr>
Magento 1.9.1.1<\/td>CE-1.9.1.1<\/a><\/td><\/tr>
Magento 1.9.1.0<\/td>CE-1.9.1.0<\/a><\/td><\/tr>
Magento 1.9.0.1<\/td>CE-1.9.0.1<\/a><\/td><\/tr>
Magento 1.8.1.0<\/td>CE-1.8.1.0<\/a><\/td><\/tr>
Magento 1.8.0.0<\/td>CE-1.8.0.0<\/a><\/td><\/tr>
Magento 1.7.0.2<\/td>CE-1.7.0.2<\/a><\/td><\/tr>
Magento 1.6.2.0<\/td>CE-1.6.2.0<\/a><\/td><\/tr>
Magento 1.6.1.0<\/td>CE-1.6.1.0<\/a><\/td><\/tr>
Magento 1.5.1.0<\/td>CE-1.5.1.0<\/a><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
How to check if Magento SUPEE 6788 has been installed correctly?<\/h3>\n\n\n\n
Use magereport.com<\/a> to check the accuracy of the installation process.<\/p>\n\n\n\n
Magento SUPEE 6788 Installation Possible Issues:<\/h3>\n\n\n\n
After Magento SUPEE 6788 installation, if you don\u2019t get bash output like \u201cPatch was applied\/reverted successfully\u201d, check the output for any issues. If the issue still persists, it is recommended to update the .htaccess file. First of all, take a backup and replace the default one. If it doesn\u2019t help, we provide advanced solution to follow but implemet it on your own responsibility.<\/p>\n\n\n\n
Simply remove the lines 163-195 from the patch file which should start with:<\/p>\n\n\n\n
diff --git .htaccess .htaccess<\/code><\/pre>\n\n\n\n
and end with:<\/p>\n\n\n\n
+ <\/code><\/pre>\n\n\n\n
Additionally, if it helps apply the patch, simply add below lines at the end of your .htaccess file:<\/p>\n\n\n\n
## Deny access to cron.php\n<Files cron.php>\n\n    ############################################\n    ## uncomment next lines to enable cron access with base HTTP authorization\n    ## http:\/\/httpd.apache.org\/docs\/2.2\/howto\/auth.html\n    ##\n    ## Warning: .htpasswd file should be placed somewhere not accessible from the web.\n    ## This is so that folks cannot download the password file.\n    ## For example, if your documents are served out of \/usr\/local\/apache\/htdocs\n    ## you might want to put the password file(s) in \/usr\/local\/apache\/.\n\n    #AuthName \"Cron auth\"\n    #AuthUserFile ..\/.htpasswd\n    #AuthType basic\n    #Require valid-user\n\n    ############################################\n\n    Order allow,deny\n    Deny from all\n\n<\/Files><\/pre>\n\n\n\n
Now check if any file has been infected with patch file override. Most of the updated files reside in core structure and they shouldn\u2019t be affected but still it\u2019s wise decision to check files below to check after patch installation:<\/p>\n\n\n\n