Session serializer mismatch can lead to remote code execution.
Session upload progress, when enabled, can store attacker-controlled data in a session key using the php_binary or php_serialize session serializer. If the same session is later read with the php serializer, because session.serialize_handler is changed at runtime or differs between applications sharing a session store, bytes inside the key can be passed to the unserializer. A remote attacker able to submit a multipart upload can inject objects, which may lead to code execution when the reading application contains a suitable gadget chain, or to session corruption or denial of service.
This issue affects PHP versions before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
8.2.368.3.378.4.288.5.138.2.368.3.378.4.288.5.138.2.368.3.378.4.288.5.138.2.368.3.378.4.288.5.138.2.368.3.378.4.288.5.138.2.368.3.378.4.288.5.138.2.368.3.378.4.288.5.138.2.368.3.378.4.288.5.138.2.368.3.378.4.288.5.138.2.368.3.378.4.288.5.13Exploitability
AV:NAC:HAT:PPR:NUI:NVulnerable System
VC:HVI:HVA:HSubsequent System
SC:NSI:NSA:N9.2/CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NInput Validation
Serialization