{"id":63,"date":"2018-03-13T23:34:03","date_gmt":"2018-03-13T23:34:03","guid":{"rendered":"https:\/\/meetanshi.com\/blog\/2018\/03\/13\/install-magento-supee-7405-with-or-without-ssh\/"},"modified":"2025-09-01T11:12:23","modified_gmt":"2025-09-01T05:42:23","slug":"install-magento-supee-7405-with-or-without-ssh","status":"publish","type":"post","link":"https:\/\/meetanshi.com\/blog\/install-magento-supee-7405-with-or-without-ssh\/","title":{"rendered":"How to Install Magento SUPEE 7405 with or without SSH"},"content":{"rendered":"\n

Security in E-commerce stores is very important. Magento knows its important and make available Security Patches on timely basis to the store owners to protect stores from potential threats and attack and ensure smooth functioning.<\/p>\n\n\n\n

One such Security Patch Magento SUPEE 7405<\/strong><\/em><\/a> was released on February 23, 2016. The installation of the patch enables support for PHP 5.3 and address issues with upload file permissions, merging carts, and SOAP APIs.<\/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.6<\/a> rather than installing Magento SUPEE-7405<\/strong><\/em>.<\/p>\n\n\n\n

Installation of Security Patch Magento SUPEE 7405<\/h2>\n\n\n\n

There are two methods for the installation process of Magento SUPEE 7405<\/em> which are discussed as below:<\/p>\n\n\n\n

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

Contact your hosting provider if you don\u2019t know how to set up SSH. Download Magento SUPEE 7405<\/strong> Patch files for your Magento Version from here<\/a>.<\/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-7405_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 7405 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<\/strong><\/th>SUPEE 7405<\/strong><\/th><\/tr><\/thead>
Magento 1.9.2.2<\/td>CE-1.9.2.2<\/a><\/td><\/tr>
Magento 1.9.2.1<\/td>CE-1.9.2.1<\/a><\/td><\/tr>
Magento 1.9.1.1<\/td>CE-1.9.1.1<\/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.7.0.2<\/td>CE-1.7.0.2<\/a><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
How to check if Magento SUPEE 7405 has been installed correctly?<\/h3>\n\n\n\n
Visit magereport.com<\/a> to check the correctness of the process.<\/p>\n\n\n\n
Possible issues in Installation of Magento SUPEE 7405:<\/h3>\n\n\n\n
    \n
  1. PHP version issue<\/strong>
    It is recommended to use latest PHP versions i.e greater or equal to PHP 5.4.0 in order to make this patch work successfully as the new short format only works with latest PHP verions.<\/li>\n\n\n\n
  2. Admin panel login issue<\/strong>
    Immediately after patching, you may not be able to login to admin panel. To resolve the issue, you have to take away every session file and remove other session storage types and delete browser cookies in order to avoid difficulty in logging into the admin panel.<\/li>\n\n\n\n
  3. Image upload issue resulted from incorrect file permission for newly uploaded images<\/strong>
    The patch affect file permission of the image uploaded from Magento backend. Before patching, image files used to have 0777 permission which gets changed to 0640 and 0750 which make them inaccessible for users. There are two ways to resolve this issue:\n