{"id":364,"date":"2025-04-15T16:30:00","date_gmt":"2025-04-15T15:30:00","guid":{"rendered":"https:\/\/davagordon.co.uk\/blog\/?p=364"},"modified":"2025-04-21T20:20:54","modified_gmt":"2025-04-21T19:20:54","slug":"how-to-apply-a-magento-2-patch-without-composer-step-by-step","status":"publish","type":"post","link":"https:\/\/davagordon.co.uk\/blog\/how-to-apply-a-magento-2-patch-without-composer-step-by-step\/","title":{"rendered":"How to Apply a Magento 2 Patch Without Composer (Step-by-Step)"},"content":{"rendered":"\n

Keeping your Magento 2 store secure and up to date is not just best practice, it\u2019s essential. Every unpatched vulnerability leaves your store open to potential exploits, risking customer trust and site stability. In this guide, you\u2019ll learn how to apply a Magento 2 patch<\/strong> manually, without using Composer to keep your store safe and running smoothly.<\/p>\n\n\n\n

This guide walks you through how to manually apply a Magento 2 patch (commonly provided in .composer.patch<\/code> format), using the recent Adobe Commerce APSB24-40 security update as an example.<\/p>\n\n\n\n

Step-by-Step Guide to Manually Applying a Magento 2 Patch<\/p>\n\n\n\n

Step 1: Download the Patch<\/strong><\/h3>\n\n\n\n

Visit Adobe’s official Security Bulletins<\/a> and navigate to the patch relevant to your Magento 2 version. For this guide, we\u2019ll reference:<\/p>\n\n\n\n

\ud83d\udd17 Adobe Commerce APSB24-40 Patch<\/a><\/p>\n\n\n\n

Be sure to choose the patch that matches your exact Magento version<\/strong>, such as 2.4.6-p5 or 2.4.5-p6.<\/p>\n\n\n\n

Step 2: Unzip the Patch File<\/strong><\/h3>\n\n\n\n

Once downloaded, unzip the .zip<\/code> archive. Inside, you’ll typically find one or more files ending in .composer.patch<\/code>.<\/p>\n\n\n\n

Example:<\/p>\n\n\n\n

VULN-27015-2.4.6x.composer.patch<\/code><\/pre>\n\n\n\n
Step 3: Apply the Patch Manually<\/strong><\/h3>\n\n\n\n
    \n
  1. SSH into your server<\/strong> and navigate to the Magento root directory<\/li>\n<\/ol>\n\n\n\n
      \n
    1. <\/li>\n<\/ol>\n\n\n\n
      cd \/path\/to\/your\/magento2\/root<\/code><\/pre>\n\n\n\n
          2. Run the patch command<\/strong>: <\/p>\n\n\n\n
        \n
      1. <\/li>\n<\/ol>\n\n\n\n
        patch -p1 < VULN-27015-2.4.6x.composer.patch<\/code><\/pre>\n\n\n\n
        Replace the filename above with the actual name of your patch file.<\/p>\n\n\n\n
        \ud83d\udca1 Note<\/strong>: The -p1<\/code> option tells the patch command how to interpret file paths inside the patch. If you see \u201cfile not found\u201d errors, try adjusting the -p<\/code> number (e.g., -p0<\/code>, -p2<\/code>) depending on your directory structure.<\/p>\n\n\n\n
        Step 4: Clear Cache and Recompile<\/strong><\/h3>\n\n\n\n
        After applying the patch, clear Magento\u2019s cache and recompile (if necessary):<\/p>\n\n\n\n
        php bin\/magento cache:clean\nphp bin\/magento cache:flush\nphp bin\/magento setup:di:compile<\/code><\/pre>\n\n\n\n
        Step 5: Verify the Patch Was Successful<\/strong><\/h3>\n\n\n\n
        Don’t stop at applying the patch, validate<\/strong> it.<\/p>\n\n\n\n