Adobe Commerce and Magento CVE-2026-48356: file upload flaw and APSB26-73 patch

Venus Yazılım5 min read

CVE-2026-48356 in Adobe Commerce and Magento allows dangerous file uploads. Affected versions, the APSB26-73 patch, and the checks to run now.

If your store has not received Adobe’s APSB26-73 update, an attacker may be able to upload files to your server and change the pages your customers see. CVE-2026-48356 affects Adobe Commerce and Magento, and CISA has added it to its Known Exploited Vulnerabilities catalog.

Short answer: CVE-2026-48356 lets an attacker upload dangerous file types to Adobe Commerce and Magento Open Source (CWE-434). NVD scores it 9.3 (Critical) under CVSS 3.1. No login is required, but the attack needs the victim to open a malicious link or interact with a compromised page. Adobe fixes it in APSB26-73; for Magento Open Source, move to 2.4.6-2026-jul, 2.4.7-2026-jul, 2.4.8-2026-jul, or 2.4.9-2026-jul.

At a glance

Field Detail
CVE CVE-2026-48356
CVSS 9.3 (v3.1), NVD score, Critical. Adobe’s bulletin lists the same CVE at 9.6.
Weakness type Unrestricted upload of a file with a dangerous type (CWE-434)
Authentication Not required. The attack needs the victim to take an action, such as opening a malicious link or interacting with a compromised page.
Active exploitation Listed in CISA KEV. Sansec documented an attack wave that used this flaw. Adobe’s bulletin, last updated 11 August 2026, said it was not aware of exploits at that time.
CISA KEV added 27 October 2026. Due date for federal agencies: 10 November 2026.
Fixed versions Adobe Commerce: “2026-jul” patches for 2.4.4 through 2.4.9. Magento Open Source: 2.4.6-2026-jul, 2.4.7-2026-jul, 2.4.8-2026-jul, 2.4.9-2026-jul.

What happened?

The flaw comes from weak checks on uploaded file types. If the server accepts a file that it can run, an attacker can run commands on the store server.

In the campaign Sansec documents (which it calls PolyShell), attackers used this flaw to upload PHP web shells. They then injected a script into the store’s CMS blocks, which are content fragments shown on storefront pages. The script runs in visitors’ browsers and sends details such as the page title and referrer to an external server. Sansec reports that 953 stores were hit in its broader CMS block campaign since July 2025. That figure is not limited to this CVE.

Who is affected?

Adobe’s bulletin lists these affected versions:

  • Magento Open Source: 2.4.9 (unpatched), 2.4.8-p5 and earlier, 2.4.7-p10 and earlier, 2.4.6-p15 and earlier.
  • Adobe Commerce: 2.4.9, 2.4.8-p5 and earlier, 2.4.7-p10 and earlier, 2.4.6-p15 and earlier, 2.4.5-p17 and earlier, 2.4.4-p18 and earlier.
  • Adobe Commerce B2B: 1.5.3, 1.5.2-p5 and earlier, 1.4.2-p10 and earlier, 1.3.4-p17 and earlier, 1.3.3-p18 and earlier.
  • Adobe Commerce Events: 1.6.0 through 1.20.0. The fix is 1.21.0.

Magento Open Source 2.4.5 and earlier are not listed in this bulletin. If you run one of those versions, ask Adobe for a clear upgrade path.

What should you do?

  1. Check your version. From the Magento root directory:
bin/magento --version

Compare the output with the list above.

  1. Apply the APSB26-73 patch. Adobe recommends updating to the newest version. Release notes are linked from Adobe’s KA-37421 entry. Test the update in a staging environment before you deploy it to production.

  2. Check again after patching. Sansec reports that patched stores, including some on 2.4.7-p10, were also infected. A patch closes the hole. It does not remove an existing compromise. Run the checks below.

  3. Rotate credentials after cleanup. Sansec advises rotating database, admin, and API integration passwords. Deleting the injected scripts alone does not remove an attacker’s access.

  4. Patch the related issue too. Sansec’s report on the same campaign also names CVE-2025-54236 (SessionReaper) and Adobe bulletin APSB25-88.

  5. If you must delay the update. The Adobe bulletin we reviewed lists no temporary workaround. Sansec says its commercial product, Sansec Shield, can block these attack attempts in real time. That is a vendor recommendation, not an Adobe one, and it does not replace the patch.

Have I been hit?

Sansec’s reports list these indicators:

  • Backdoor file name: accesson.php. Sansec says it was dropped across several directories.
  • localStorage keys: 136c1e07507f4a97, 136c1e07507f4a98, fpCode.
  • Loader and redirect domains: lanhd6549tdhse.top, deepveindrilling.com, additionalver.com, neswnsssn.click, manulfie.click. Sansec publishes the full URL list in its IoC section.
  • Database locations: the content column of cms_block and the cms_page table. Look for unexpected writes and recent update_time values.
  • Filesystem: unexpected files under pub/media/custom_options/ and pub/media/customer_address/.
  • Admin accounts: unfamiliar users in admin_user.

Sansec does not list file hashes or IP addresses. Limit your checks to these indicators. If you find nothing, that does not prove your store is clean. Also review web server access logs and unexpected cron jobs.

Frequently asked questions

I run Magento 2.4.7-p10. What should I do?

Adobe lists 2.4.7-p10 as affected. If you have not applied the patch, update now and run the checks above. If you have applied it, you still need to check CMS blocks and admin accounts.

Does a firewall or WAF close this vulnerability?

The sources we reviewed recommend a commercial blocking product. That is a temporary measure. It does not replace Adobe’s patch.

Does an attacker need admin access?

No. Adobe’s bulletin says no authentication is required. The attack still needs the victim to open a malicious link or interact with a compromised page.

Adobe said there were no known exploits. Why did CISA add it to KEV?

Adobe’s bulletin was last updated on 11 August 2026. CISA made its decision later, and Sansec documented an attack wave using this flaw in the same period. Weigh the vendor statement against these newer sources.

Sources

If you want help patching your store or checking it for compromise, take a look at our e-commerce service.

More notes

  1. 4 min read

    Google Brotli CVE-2026-111497: memory overflow in Node.js and Brotli libraries

    A memory overflow in the Brotli decoder (CVE-2026-111497) can lead to code execution without logging in. Update Node.js and Brotli.

  2. 5 min read

    Cisco ASA and FTD CVE-2026-76418: SSL VPN reload flaw and fixed releases

    Unauthenticated attackers can reload Cisco ASA and FTD devices through SSL VPN when secondary authentication is set. It is being exploited. Check and upgrade.

Let’s reserve a slot in the rack.

Describe your project in a few steps and we’ll prepare a written proposal with scope, timeline and an infrastructure plan.

Request a quoteor write directly: email address