On 6 November 2026 TrendAI Research published a warning about two Adobe Commerce and Magento Open Source flaws that attackers are using going into the holiday shopping season: PolyShell (CVE-2026-48356) and StyleSmuggler (CVE-2026-75650). Neither is new, and we have covered both before. What is new is the timing. Black Friday traffic is weeks away, and TrendAI's main point is one many stores miss: a patch closes the way in, but it does not remove an attacker who got in before the patch.
The two ways in
PolyShell is an unrestricted file upload flaw. According to the TrendAI write-up, which cites Sansec, an attacker without a login sends a request to the guest cart API with a file that looks like an image but also contains PHP. The upload check only looks at the image header, so the file is saved on the server, and whether it runs depends on how the web server is configured. CISA added it to its Known Exploited Vulnerabilities catalogue on 27 October, and MageBytes notes that US federal agencies have until 10 November to fix it. That is today. Our earlier post, PolyShell is now on CISA's exploited list, has more background.
StyleSmuggler is an unauthenticated server-side template injection that leads to remote code execution. A request to /paypal/transparent/response/ writes attacker PHP into var/report/, and a GraphQL request with crafted styles values then loads and runs it. Imperva tracked a coordinated campaign between 9 and 13 September 2026 across Western Europe, North America and Asia-Pacific that used it to install PSK Agent, an obfuscated Go remote access trojan, and in some cases a PHP web shell. Adobe's hotfix VULN-39341 closes the entry point. Adobe's October bulletin APSB26-153 reminds merchants to apply the CVE-2026-75650 hotfix in addition to that month's security update.
Why the timing matters
Both flaws give the attacker code execution on the store server. From there, TrendAI says, they can read store secrets, plant web shells and inject card skimmers into the checkout page. A skimmer added in November collects card data during the busiest weeks of the year, and it often goes unnoticed until a payment provider or a customer reports fraud. If your store was unpatched at any point since March (PolyShell) or early September (StyleSmuggler), assume it may have been touched and check before the peak, not after.
A pre-peak checklist
This list follows the steps TrendAI recommends. Do it with your developer or hosting team, and keep notes on what you found.
- Confirm the patches. Check that the PolyShell fix and the StyleSmuggler hotfix VULN-39341 are both applied, together with the current monthly security update for your release line. A hotfix that was skipped in one environment is a common gap.
- Stop PHP running from uploads. Make sure the web server will not run PHP from media and upload directories such as
pub/media/. This limits what a planted file can do even if another upload bug appears. - Hunt for files that should not be there. Look for unexpected files under
pub/media/custom_options/quote/andpub/media/, files namedzer4.phport4.php, and new files invar/report/. - Check processes and scheduled jobs. Look for PSK Agent processes and for changes to cron, system configuration and CMS blocks that nobody on the team made.
- Inspect the checkout. Load the checkout page and review the scripts it pulls in. An injected script there is the skimmer case.
- Rotate secrets if the server may have been reached. That means the secrets in
app/etc/env.php. If you find signs of compromise, treat the server as fully compromised and bring in an incident response specialist rather than just deleting the files you found.
Freeze changes, but not security
Many teams start a code freeze in November so nothing breaks during the sales. That is sensible for features, but security patches and the compromise check above should not wait for January. A short, tested patch window now is much cheaper than cleaning up a skimmer in December.
Where Claspwell fits
Claspwell is a catalog-aware AI sales assistant for Magento 2 and Hyvä, not a security product, and it does not patch or scan your store. We mention it here because any extension or widget you add to a store becomes part of what you need to keep an eye on. The Claspwell widget uses a public store key with origin checks, and no secrets or OpenAI keys are sent to the browser. If you are reviewing third-party scripts on your storefront before the holidays, our chat widget security checklist for Magento lists what to ask any vendor.
Sources: TrendAI Research, 6 November 2026, Imperva on PSK Agent, Adobe security bulletin APSB26-153, MageBytes October 2026 roundup.