| Title | e107.org e107 CMS 2.3.3 Deserialization |
|---|
| Description | The installer accepts a POST parameter previous_steps, performs base64_decode() and then calls unserialize() directly on that input without validation. Because unserialize() can instantiate arbitrary PHP objects when given attacker-controlled serialized object data, an attacker can craft data that triggers magic methods (for example __wakeup() or __destruct()) in existing classes that perform sensitive actions (file write/delete, command execution, database ops). This can lead to arbitrary file manipulation, privilege escalation within the PHP process context, or remote code execution (RCE), depending on the codebase classes available and the deployment environment. |
|---|
| Source | ⚠️ https://github.com/lakshayyverma/CVE-Discovery/blob/main/e107%20CMS.md |
|---|
| User | lakshay12311 (UID 91298) |
|---|
| Submission | 10/05/2025 14:11 (8 months ago) |
|---|
| Moderation | 10/16/2025 13:51 (11 days later) |
|---|
| Status | Duplicate |
|---|
| VulDB entry | 327949 [e107 CMS up to 2.3.3 POST Parameter install.php base64_decode previous_steps deserialization] |
|---|
| Points | 0 |
|---|