Five Wrong Assumptions About the Magento SessionReaper Flaw
CVE-2025-54236 combines a critical CVSS score, active exploitation, and a complicated operational response. The result is a stream of shortcuts: patch and move on, block one URL, trust the WAF, or assume a clean file scan settles the case. Each shortcut leaves part of the risk unexamined.
Vulnerability overview
Adobe APSB25-88 covers an improper input validation vulnerability in Adobe Commerce and Magento Open Source. The CVSS 3.1 score is 9.1, with no required authentication or user interaction. Adobe confirmed exploitation in the wild.
Sansec named the issue SessionReaper and reported a path involving a malicious session and nested deserialization in Magento's REST API. The observed attacks also used /customer/address_file/upload to write PHP payloads as fake sessions. The researcher describes customer account takeover and unauthenticated RCE under certain conditions, not a uniform outcome for every vulnerable storefront.
Assumption one: every affected store is exploitable in the same way
Patch level, session adapter, web-server execution rules, extensions, and request routing all affect the path from the CVE to code execution. Sansec says its specific RCE route appeared to require file-based sessions, while advising other session backends to patch because other abuse paths may exist. Treat configuration diversity as a reason for targeted validation, not as a reason to delay.
Assumption two: the vendor patch removes attacker access
The patch closes the known defect. It does not remove a webshell, malicious session, altered CMS block, administrator account, or API integration created before the update. A late-patching store needs a compromise review. Sansec recommends crypt-key rotation, administrator password resets, and removal of unknown integrations after confirmed compromise.
Assumption three: blocking one upload URL is enough
Sansec warned that blocking /customer/address_file/upload alone is insufficient because the controller can be reached through multiple paths. File permissions, web-server behavior, route restrictions, and application configuration all belong in the control set. The goal is to make user-writable content non-executable across the upload surface, including alternate routes to the controller.
Assumption four: scanner evasion means the store is clean
The 2026 loader campaign checks browser fingerprints and changes its response for automated clients. A scanner that receives an empty page may still be looking at an infected store. Detection needs database review, browser-side evidence, content-security-policy telemetry, and comparison across different clients. A clean scanner response is weak evidence when the payload is designed to hide from scanners.
Assumption five: a KEV listing replaces internal triage
CISA added CVE-2025-54236 on October 24, 2025, with a November 14 federal deadline. That listing establishes exploitation and urgency. It does not identify which of an organization's Magento sites run an affected release, which use file-backed sessions, or which are already compromised.
Affected products and scope
Adobe lists affected Adobe Commerce through 2.4.9-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, and 2.4.4-p15. Adobe Commerce B2B has separate ceilings through 1.5.3-alpha2, 1.5.2-p2, 1.4.2-p7, 1.3.4-p14, and 1.3.3-p15. Magento Open Source is affected through the listed 2.4.5 to 2.4.9 releases. The emergency hotfix covers 2.4.4 through 2.4.7.
Exposure context
ZoomEye stored 134,273 matches for app="Magento" and 134,273 for vul.cve="CVE-2025-54236". The Search query supplied the selected link on the tie. This is a product-fingerprint count, not a confirmed list of vulnerable or infected stores.
What to do instead
Build an asset list with version and owner. Patch or mitigate every affected release using the correct vendor path. Test the customer-address flow and session behavior. Add temporary WAF coverage, then verify it against the routes and encodings the store actually accepts.
After late patching or suspicious activity, preserve evidence, inspect file storage and CMS records, invalidate sessions, rotate the crypt key, reset administrator credentials, and remove unknown integrations. Recheck from a clean browser and an automated client because payload behavior can differ. Finish with monitoring for renewed access and a documented owner for follow-up.
Top comments (0)