Skip to content

Commit e9467cd

Browse files
Chocapikkjheysel-r7
andcommitted
Clarify file-based session storage requirements and exploit limitations
Co-authored-by: jheysel-r7 <jheysel-r7@users.noreply.github.com>
1 parent c8ec6e2 commit e9467cd

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

documentation/modules/exploit/multi/http/magento_sessionreaper.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,14 @@ allows an unauthenticated user to gain arbitrary code execution through nested d
55
upload.
66

77
This vulnerability (CVE-2025-54236, also known as SessionReaper) affects Magento 2.x instances using file-based session
8-
storage. The module was specifically tested against Magento 2.4.4.
8+
storage. **Note:** File-based session storage is not enabled by default in Magento. The target must be explicitly
9+
configured to use file-based sessions (typically via `app/etc/env.php` with `'session' => ['save' => 'files']`) for this
10+
vulnerability to be exploitable. By default, Magento uses database or Redis session storage.
11+
12+
**Exploit limitations:** In production environments, the upload directory (`media/customer_address/`) where the malicious
13+
session file is uploaded is generally configured as read-only, which prevents successful exploitation. This exploit
14+
therefore has limited applicability in hardened production environments. The module was specifically tested against
15+
Magento 2.4.4.
916

1017
### Description
1118

0 commit comments

Comments
 (0)