This question already has an answer here:

I've installed the patch SUPEE-6482, but still appear a window like this:


Whether it means the patch is not installed correctly? How to ensure that our website/Magento is secure from the patch issue? I mean sample case on release notes of SUPEE-6482 (two issues related to APIs and two cross-site scripting risks), whether sufficient in tests on web like https://shoplift.byte.nl/ or need special check?

marked as duplicate by Fabian Schmengler, saravanavelu, Keyul Shah, brentwpeterson, AreDubya Aug 14 '15 at 15:50

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • This is just the default admin panel message that pops up. You need to either mark as read or delete the message inside the message inbox in your Magento admin panel. – BENN1TH Aug 15 '15 at 0:54
  • Thanks @benn1th, I know that it is a message pop up from Magento and how to remove it or disable that message. I mean sample case on the release notes of SUPEE-6482 (two issues related to APIs and two cross-site scripting risks) from, whether sufficient in tests on web like shoplift.byte.nl or special need to check? – Andhi Irawan Aug 18 '15 at 1:24
  • 1
    Check in app/etc/applied.patches.list to see what is reported as installed, check the file dates on the patched files to make sure they match the application date in the list or open the patch and manually verify that the changes were made to the listed files. The Admin notification doesn't have any intelligence that is able to detect that patches are installed. It's just a notification that you need to manually verify your patches were installed. The ShopLift tester is for a way earlier patch, has nothing to do with the latest API patch and doesn't test for it. – Fiasco Labs Aug 18 '15 at 3:17
  • Thanks @fiasco-labs, but I can't find / there's no applied.patches.list in app/etc/ – Andhi Irawan Aug 18 '15 at 8:00
  • 1
    Yes, then the only way to check is to physically diff the patched file against one freshly extracted from an installer archive file that matches your installed version. Or else the file date for that particular file must match the patched file that you uploaded. – Fiasco Labs Aug 19 '15 at 3:09