ZeroBreach Request early access
← All Attack Surface
critical CVE-2026-48356

Adobe Commerce and Magento file upload flaw under active exploitation, added to CISA KEV (CVE-2026-48356)

Tags: php, adobe-commerce, magento-open-source, exploited

Adobe Commerce and Magento Open Source contain an unrestricted upload of a file with a dangerous type flaw (CVE-2026-48356, CVSS 9.3 in the Adobe CVE record) that can result in arbitrary code execution in the context of the current user. Exploitation requires user interaction, in that a victim must visit a maliciously crafted URL or interact with a compromised web page, and the scope is changed, so the impact reaches resources outside the vulnerable component.

Affected releases are Adobe Commerce 2.4.9, 2.4.8-p5 and earlier patch levels, 2.4.7-p10 and earlier, 2.4.6-p15 and earlier, 2.4.5-p17 and earlier, and 2.4.4-p18 and earlier, with matching Adobe Commerce B2B lines, Magento Open Source 2.4.9, 2.4.8-p5 and earlier, 2.4.7-p10 and earlier, and 2.4.6-p15 and earlier, and Adobe Commerce Events 1.20.0 and earlier. The matching 2026-jul versions, such as 2.4.9-2026-jul, are unaffected. Adobe published the fix in bulletin APSB26-73 on July 14, 2026.

CISA added CVE-2026-48356 to its Known Exploited Vulnerabilities catalog on October 27, 2026, with a federal remediation due date of November 10, 2026. Security firm Sansec reported 953 online stores infected in a loader campaign linked to the flaw, including a wave that planted the loader on 471 stores in one hour through PolyShell webshells. A clean external scan does not prove a store is safe, because the loader hides from scanners and lives in database content.

What to do

  • Apply the APSB26-73 security release matching the exact installed release line, or upgrade to a supported line that carries the fix, and verify the new build version.
  • Search CMS blocks and pages in the database for script tags and loader markers that were not added by the store team, and check upload folders such as pub/media/custom_options/ for files that should not be there, including images that contain PHP code.
  • Review administrator accounts for accounts that do not belong to known users, remove any that do not belong, and turn on two-factor login for every remaining administrator.
  • If a webshell, rogue administrator, or injected script is found, rotate database, administrator, and API integration credentials, and rebuild from a known-good copy rather than cleaning in place.

A store or server with a forgotten component is the risk that recurring scans exist to catch. ZeroBreach inventories every plugin, package, and bundled library on every app it watches and flags vulnerable versions on its recurring scans, so a flaw like this does not stay unnoticed while a fix is outstanding.