file upload
5 articles with this tag
Adobe Commerce and Magento vulnerability CVE-2026-48356: CISA confirms exploitation (KEV), the July fix, and how to check for intrusion
On October 27, 2026, CISA added CVE-2026-48356, a file upload vulnerability in Adobe Commerce and Magento Open Source, to its Known Exploited Vulnerabilities (KEV) catalog. The deadline for US federal civilian agencies is November 10. Adobe fixed this flaw, along with 13 others, in security bulletin APSB26-73 on July 14, 2026. Adobe Commerce 2.4.4 to 2.4.9, Magento Open Source 2.4.6 to 2.4.9, Adobe Commerce B2B and Adobe Commerce Events are affected. The fix is the 2026-jul security fix for each release line (1.21.0 for Events). Adobe's bulletin table rates it CVSS 9.6, while Adobe's CVE record and NVD rate it 9.3; the only difference is the availability impact. Adobe's bulletin (updated August 11) still says Adobe is not aware of exploitation. On October 24, an e-commerce security company reported that web shells placed through this flaw (which it calls PolyShell) and other flaws were used to inject JavaScript into store pages, in a campaign that has reached 953 stores, mostly Magento, since July 2025, and that it found the injected code on patched stores too. As of October 28, no Japanese public agency has issued an alert and no Japanese store has disclosed being affected. This site's conclusion: Adobe Commerce and Magento stores should confirm today that the July fix is applied, and even if it is, check upload folders, CMS blocks and admin accounts for signs of intrusion.
Card-Stealing Program on the PhotoGoods (Daiko Printing) Payment Page: What People Who Paid Between August 6 and September 11 Should Do
On September 16, 2026, Daiko Printing Co., Ltd. announced unauthorized third-party access to PhotoGoods (photo-goods.com), the service it runs, and said a program able to illegally capture credit card data entered on the payment page had been installed. The program was in place from August 6 until it was removed on September 11. People who entered a card on the payment page in that period (including those who did not complete a purchase) may have had their card number, expiry date and security code exposed, along with name, address, phone number, email address and information derived from their member password (stored in a converted form). The company says it confirmed unauthorized access through system vulnerabilities and abuse of a file-upload function. The number of affected people and the actual scope are under investigation, and there was no follow-up notice as of October 7. This site's take: anyone who entered a card in that period should ask the card issuer to change the number, change the password on any other service that shares the PhotoGoods password, and ignore links in 'apology' or 'refund' messages.
CVE-2026-48939 — Unauthenticated upload to RCE in iCagenda (Joomla): explainer & fixes
The developer limits critical RCE to iCagenda 3.9.14–4.0.7 on Joomla 6.0.0–6.1.1; 4.0.8 fixes it. The Joomla 3 release 3.9.15 fixes separate guest submission. Keep those issues distinct.
CVE-2026-48908 — Unauthenticated upload to RCE in SP Page Builder (Joomla): explainer & fixes
SP Page Builder for Joomla (by JoomShaper) ≤ 6.6.1 has an unauthenticated arbitrary file upload → RCE (CVSS 10.0, in CISA KEV). The custom-icon upload reportedly ran no auth or type validation. The main fix is updating to 6.6.2, plus a compromise check (rogue admins, web shells). The durable defense is designing out the 'unauthenticated upload → RCE' pattern.
File upload vulnerabilities — preventing web shells and RCE by design
The problem with an upload vulnerability isn't 'receiving a file' — it's where you put it and whether it can execute. Unauthenticated endpoint + no type validation + stored under the web root + scripts run there = web shell → RCE. Defend in layers: (1) auth/permission + CSRF on the endpoint, (2) server-side allow-list + content inspection, (3) store outside the web root (or disable execution), (4) randomize names, never trust user paths. Don't rely on one control; have something that can stop the attack at every step.