Note: This is a historical reference, not a current security baseline. Magento 1 is end-of-life.
November 29, 2017: Community Edition 1.9.3.7 and SUPEE-10415 Security Enhancements – 11/29/2017.
If you have SSH access, it would be more simple to apply the patch via SSH. If you have no SSH access to apply the patch, you can simply upgrade your installation to Magento 1.9.3.7 version which includes all the latest security patches (SUPEE-5344, SUPEE-5994, SUPEE-6285, SUPEE-6482, SUPEE-6788, SUPEE-7405, SUPEE-8788, SUPEE-9652, SUPEE-9667, SUPEE-10266, SUPEE-10336 and SUPEE-10415). If Magento upgrade is not possible in the moment due to some reason you still can apply the patch via FTP/sFTP upload as shown in this article. If you wish to save time and have us to install these patches for you, simply click here to order installation.

Preparations

    Applying Magento patches via FTP/sFTP or FileManager / File Upload

    To apply patches in this way we simply replace changed files. This way can not be used blindly if you or your developers have changed any core Magento files (which is a big no-no, by the way). Such changes should be re-applied to patched files, or you loose these changes. The following files are changed by SUPEE-10415 (v1 for 1.9.2.4 relased on November 29, 2017):
    app/Mage.php
    app/code/core/Mage/Adminhtml/Block/Report/Review/Detail.php
    app/code/core/Mage/Adminhtml/Block/Report/Tag/Product/Detail.php
    app/code/core/Mage/Adminhtml/Block/Review/Add.php
    app/code/core/Mage/Adminhtml/Block/Review/Edit/Form.php
    app/code/core/Mage/Adminhtml/Controller/Action.php
    app/code/core/Mage/Adminhtml/Model/LayoutUpdate/Validator.php
    app/code/core/Mage/Adminhtml/Model/System/Config/Backend/Filename.php
    app/code/core/Mage/Api/Helper/Data.php
    app/code/core/Mage/Api/Model/Server/Adapter/Soap.php
    app/code/core/Mage/Api/Model/Wsdl/Config.php
    app/code/core/Mage/Api/Model/Wsdl/Config/Base.php
    app/code/core/Mage/Core/Helper/String.php
    app/code/core/Mage/Core/Model/File/Validator/Image.php
    app/code/core/Mage/Core/etc/config.xml
    app/code/core/Mage/Core/etc/system.xml
    app/code/core/Mage/Customer/Model/Customer.php
    app/code/core/Mage/Eav/Model/Entity/Attribute/Backend/Serialized.php
    app/code/core/Mage/Log/Helper/Data.php
    app/code/core/Mage/Rule/Model/Abstract.php
    app/code/core/Mage/Sales/Block/Adminhtml/Billing/Agreement/Grid.php
    app/code/core/Zend/Form/Decorator/Form.php
    app/design/adminhtml/default/default/template/backup/dialogs.phtml
    app/design/adminhtml/default/default/template/sales/billing/agreement/view/tab/info.phtml
    app/design/adminhtml/default/default/template/xmlconnect/edit/tab/content.phtml
    app/design/adminhtml/default/default/template/xmlconnect/edit/tab/design/image_edit.phtml
    app/locale/en_US/Mage_Adminhtml.csv
    app/locale/en_US/Mage_Customer.csv
    js/mage/adminhtml/backup.js
    lib/Varien/Filter/FormElementName.php
    
    To install the patch via FTP/File Upload
    • select patch bundle archive corresponding to your Magento version from the table below and unpack it
    • upload all files and folders to Magento root directory of your store, replacing all files
    Magento versionSUPEE-10415 v1
    Magento 1.9.3.6SUPEE-10415-1.9.3.6
    Magento 1.9.3.4SUPEE-10415-1.9.3.4
    Magento 1.9.3.3SUPEE-10415-1.9.3.3
    Magento 1.9.3.2SUPEE-10415-1.9.3.2
    Magento 1.9.3.1SUPEE-10415-1.9.3.1
    Magento 1.9.3.0SUPEE-10415-1.9.3.0
    Magento 1.9.2.4SUPEE-10415-1.9.2.4
    Magento 1.9.2.3SUPEE-10415-1.9.2.3
    Magento 1.9.2.2SUPEE-10415-1.9.2.2
    Magento 1.9.2.1SUPEE-10415-1.9.2.1
    Magento 1.9.2.0SUPEE-10415-1.9.2.0
    Magento 1.9.1.1use SUPEE-10497
    Magento 1.9.1.0SUPEE-10415-1.9.1.0
    Magento 1.9.0.1SUPEE-10415-1.9.0.1
    Magento 1.8.1.0SUPEE-10415-1.8.1.0
    Magento 1.7.0.2SUPEE-10415-1.7.0.2
    Downloads for other versions added to table on demand when we patch certain version via file upload for the first time.

    Verification and flush of PHP opcode cache

    Test that your store is working. If you use PHP opcode caches (APC/XCache/eAccelerator) make sure to flush it after patching (or restart webserver), otherwise code will continue to run from caches. If you have any difficulties with applying the patches please let us know in comments, so we can find the solution together.

    Comments

    Archived discussion

    1. ketan
      Which file we have to download for Magento version 1.8.0
    2. Lalit Malav
      my store on 1.8.1.0. so which one is for me ?? or you will upload ASAP ??
    3. Mark
      1.8.1.0 Please
      1. magentary
        JFYI, 1.8.1.0 was recently added: http://magentary.com/wph/co…
    4. Matt
      1.9.0.1 please. Hunk on mage.php complaining about different line endings. :(
      1. Tom
        Hi, have you installed the previous patch, because it is only available for the 1.9.1.0 version (super-9767, supee-10266), does it work on the 1.9.0.1? Thank you
    5. Denis
      Error 520 Ray ID: 3c58179c88386379 • 2017-11-29 19:49:47 UTC Web server is returning an unknown error
    6. Ashwani

      Hi,

      I am getting server error while downloading patch. Please fix this as I haev to install this patch on my website. Thanks.

      Error 520 Ray ID: 3c5bc0fbdb446fe4 • 2017-11-30 06:29:43 UTC

      Web server is returning an unknown error

    7. Scode
      Thank you again :)
    8. Darren Douglas
      Is it possible to get for 1.9.2.3? Or does the 1.9.2.4 work on it :/ Don’t want to risk it!
    9. Jeff Goss
      1.9.1.0? :)
      1. Jeff Goss
        Thank you! Very very much appreciated :)
    10. Store Owner

      Hi,

      I am getting server error while downloading patch. Please fix this as I haev to install this patch on my website. Thanks.

      Error : 520 Ray ID: 3c63f5f7ff8c69d7 • 2017-12-01 06:23:59 UTC

      Web server is returning an unknown error

    11. Ashwani Rana

      I am trying to install SUPEE-10415 from your website and it is giving me an error.

      Error 520 Ray ID: 3c7c0753992231c8 • 2017-12-04 04:30:09 UTC Web server is returning an unknown error

      Many peoples already mentioned this in the comment section of this patch installation page https://magentary.com/kb/in… . I don’t know why it is taking time to respond to our queries. I am following your website for installing patches to my magento store, this is the first time I am facing this issue and the problem is that my client is getting mad on me for delaying this thing. Please try to figure out the issue so that we can do our work. Thanks in advance.

      1. Shamma Lammadingdong
        “I don’t know why it is taking time to respond to our queries.” They offer this for free. If you want a faster response, pay for it. Stop being ungrateful.
    12. Leonel Nunes
      Hello, can you please upload this one to version 1.8.1.0? Thanks in advance!
      1. magentary
        JFYI, 1.8.1.0 was recently added: https://magentary.com/wph/c…
        1. Leonel Nunes
          Thanks :)
    13. The Original Motherfucker
      Will it work in 1.7.0.1? i only see the patch for 1.7.0.2
      1. magentary
        Yes, it will. The only difference between Magento 1.7.0.1 and 1.7.0.2 is one critical security breach (RCE), so it is more vital to patch 1.7.0.1 up to 1.7.0.2 at least.
    14. Eddie May
      Just encountered “Unsupported data type N” error on #magento 1.9.2.4 after applying patch SUPEE-10415. Uploading lib/Unserialize from 1.9.3.7 fixed it
    15. janmesh

      hello, /support team

      After insatlled “SUPEE-10415-1.9.3.6” in my site site give 404 page not found error.

      please help my site is live.

      Thanks,

      1. magentary
        I’d suggest to rollback any actions you performed on your store or restore backup.
    16. Shamma Lammadingdong
      I get a “Cannot send headers; headers already sent in…app/code/core/Mage/Core/Model/Config.php, line 1245” error when refreshing the cache on Magento 1.7.0.2 after installation of the patch. Anyone else experience this?
      1. magentary
        We have patched several 1.7.0.2 installs without any issues so far. According to the error message something went wrong with config files. Probably it makes sense to check app/code/core/Mage/Core/etc/config.xml app/code/core/Mage/Core/etc/system.xml (permissions?) as these were modified in the patch and all modules configs in app/etc/modules/ as well, just in case there is some old config from deleted extension.
    17. Priyanka Singh
      Hello, Which file I have to download for magento version 1.9.1.1? Thanks
    18. vikas Chauhan
      I have tried to download the patch 10415 version 1.7.0.2. but I am getting error which is in attached screenshot. can you please help me ASAP. https://uploads.disquscdn.c…
      1. Revathi
        Am also facing same issue.
    19. Selvaganapathy Venkatesan

      Can you fix the broken link when trying to download the files?

      Error 520 Ray ID: 3d0c6f4dea8d3590 • 2017-12-21 17:06:56 UTC

      Web server is returning an unknown error

      1. gequaldev
        Yes, I am facing the same issue
    20. gequaldev
      Hello, I have tried to download the patch 10415 for version 1.9.1.0 but it is giving 520 error. Can you please fix this?
      1. gequaldev
        Can you please have a look into this issue?
    21. Anurag Khandelwal
      Why is it that the links are not working for downloading? Saw that in the comments, Magentary is replying only to those who is asking for an issue but not to one who asked for why download links are not working. Would be great if that works!
    22. Alejandro Araujo
      Files for v1.5.1.0? PLEASE :)
    23. Andi T

      After installation on 1.9.2.0 the shopping cart price rule ist broken. If I want to edit or create a rule only a blank page appears. In log file:

      ERR (3): Warning: include(Mage/Core/Helper/UnserializeArray.php): failed to open stream: No such file or directory in /lib/Varien/Autoload.php on line 94

      Has anybody the same issue?