Adobe Commerce 2.4.7-p10

Last reviewed Oct 28, 2026

Export as PDF

Prompt Details

Prompt Composition

2prompts
  1. PHP 8.3119 lines · 5.8K tokens
  2. Adobe Commerce 2.4.7-p1082 lines · 4.1K tokens
Total201 lines · 9.9K tokens

CWE Coverage

  • 20
  • 22
  • 59
  • 78
  • 79
  • 88
  • 89
  • 95
  • 98
  • 113
  • 117
  • 187
  • 201
  • 203
  • 208
  • 209
  • 214
  • 250
  • 256
  • 294
  • 295
  • 306
  • 307
  • 308
  • 319
  • 323
  • 327
  • 328
  • 338
  • 340
  • 352
  • 354
  • 359
  • 362
  • 367
  • 377
  • 384
  • 390
  • 409
  • 425
  • 434
  • 470
  • 488
  • 494
  • 502
  • 522
  • 524
  • 532
  • 552
  • 601
  • 611
  • 613
  • 614
  • 627
  • 639
  • 640
  • 674
  • 732
  • 759
  • 760
  • 770
  • 776
  • 778
  • 798
  • 807
  • 829
  • 862
  • 863
  • 915
  • 916
  • 918
  • 940
  • 942
  • 1004
  • 1021
  • 1275
  • 1287
  • 1333
  • 1336
  • 1395

Prompt Preview

Apply the PHP 8.3 baseline first. Target Adobe Commerce 2.4.7-p10 on PHP 8.3, including applicable isolated security patches. Adobe also tests this Commerce patch on PHP 8.2; using that runtime requires its matching PHP baseline. Standard support for Commerce 2.4.7 ends on 31 May 2027 and extended support on 31 May 2028.

Release-line patching

  • Keep Commerce on the newest security patch release (-pN) that Adobe's released-versions page lists for this release line, move each installed B2B or other independently versioned component to its security release compatible with that patch, and apply every isolated patch Adobe has published since then. Each -pN release is cumulative, while isolated patches are standalone files that Adobe folds into the next -pN, so a Composer version check alone does not establish isolated-patch coverage.
  • For installations using isolated monthly patches over this package, verify the complete chain of applicable monthly archives in Adobe's published release order. Each archive is non-cumulative; within each month, apply its included CE file before EE, then matching B2B and other installed-component files in their documented order. Check the latest bulletin and patch-status results rather than assuming a previous month's archive is current.
  • On Cloud, update magento/magento-cloud-patches and verify which fixes it actually applies before adding manual hotfixes. Do not apply a duplicate isolated file over the same fix supplied by Cloud Patches.
  • Apply the separate APSB26-146 hotfix for CVE-2026-75650, using the VULN-39341 archive