How to check which modules are affected by security patch SUPEE-6788

SUPEE-6788 released and admin routing changes turned off by default. This means that the patch include the fix, but that it will be disabled when installed. This will give you some additional time to make updates to your code and will give merchants flexibility to turn on this part of the patch once their extensions and customizations have been updated to work with it.

For enable admin routing capability for extensions after install the path go to Admin -> Advanced -> Admin -> Security.

Magento CE 1.4-1.6 patches are delayed and should be available in about one week!

SUPEE-6788 Resources list

  • Official details & download SUPEE-6788 - &

  • How to apply SUPEE-6788 discussion with useful tips -

  • Install SUPEE-6788 without SSH -

  • SUPEE-6788 for CE - on GitHub -

  • SUPEE-6788 for EE 1.12.x - 1.14.x on GitHub -

  • SUPEE-6788 and Backward Compatibility -

  • Community driven up to date list of Extensions that will break with SUPEE-6788 / Magento / EE -

  • Helpful Magerun commands

    • n98-magerun dev:template-var - Find non-whitelisted vars/blocks to be compatible with SUPEE-6788 and Magento
    • n98-magerun.phar dev:old-admin-routing - Find extensions that use old-style admin routing (which is not compatible with SUPEE-6788 and Magento
  • Check if store patched / affected -

  • Some of custom blocks on the front page have disappeared after patch install - APPSEC-1057 How to add variables or blocks to the white list tables &

  • Magento SUPEE-6788 Developer Toolbox - find and automatically resolve major problems from the patch

  • MageDownload CLI - A PHP tool to automate Magento release and patch downloads -

  • How to whitelist template variables and blocks for SUPEE-6788 -

  • Check Magento files for known appsec affected code -

  • Common issues with SUPEE 6788 Magento patch installation -

  • Performance improvement for Magento Patch SUPEE-6788 - , , Details -

Along the lines of other comments about detecting conflicts, we at ParadoxLabs have created a script to track down everything affected by APPSEC-1034 (admin controllers) and APPSEC-1057 (whitelist). It will also attempt to fix any bad controllers, since that's a fairly precise and invasive change to make.

It doesn't cover APPSEC-1063 (SQL injection) or APPSEC-1079 (custom options), but it would be great if it could. Not sure how to detect those with any sort of precision. We're open to contributions.

This php script might be useful in identifying Magento code affected by the proposed SUPEE-6788 patch.

This is in no way a foolproof security check for this patch, but might be useful to quickly scan your installation for the modules and code affected.

Install the script with


edit the path to your Magento installation



php magento_appsec_file_check.php

Affected files will be displayed:

*** Magento security file check ***
[1] APPSEC-1034, addressing bypassing custom admin URL
2 effected files :
<use>admin</use> found in  app/code/community/Itabs/Debit/etc/config.xml
<use>admin</use> found in  app/code/core/Mage/Adminhtml/etc/config.xml

[2] APPSEC-1063, addressing possible SQL injection
2 effected files :
collection->addFieldToFilter(' found in  app/code/community/Itabs/Debit/Model/Export/Abstract.php
collection->addFieldToFilter(' found in  app/code/community/Itabs/Debit/controllers/Adminhtml/OrderController.php
collection->addFieldToFilter(' not found.
collection->addFieldToFilter('\` not found.
collection->addFieldToFilter('\` not found.

[3] APPSEC-1057, template processing method allows access to private information
{{config path= not found.
{{block type= not found.


The script use grep to search Magento files for occurrences of the code that may possibly break backward compatibility with customizations or extensions when SUPEE-6788 is applied.