High severityPHPInsecure DeserializationHIGH confidence
Insecure Deserialization
Untrusted request input is passed to unserialize(), enabling PHP object injection and potentially remote code execution via POP gadget chains (CWE-502).
Standards mapping
- OWASP Top 10
- A08:2021 - Software and Data Integrity Failures
- OWASP ASVS
- V5.5.3 (L1)
Vulnerable vs. safe
Flagged by this check
return unserialize($data);Passes - the safe pattern
return json_decode($data, true);Why it matters & how to fix it
Untrusted request input is passed to unserialize(), enabling PHP object injection and potentially remote code execution via POP gadget chains (CWE-502). Never unserialize attacker-controlled data. Use json_decode() for data interchange; if unserialize() is unavoidable, pass ['allowed_classes' => false] to block object instantiation.
References
Rule ID integsec-php-insecure-deserialization - engine: Opengrep - license: MIT - Copyright (c) IntegSec Inc.
TurboPentest runs this check automatically
Connect a GitHub repo and this check runs on every white-box pentest - AI-validated and reported with proof, from $99 per target.
Start a pentestRelated checks
- JavaScript / TypeScript - Insecure DeserializationNode Serialize Unserialize
- JavaScript / TypeScript - Insecure DeserializationYAML Unsafe Load
- Python - Insecure DeserializationJsonpickle Decode
- Python - Insecure DeserializationPickle Load
- Python - Insecure DeserializationYAML Unsafe Load
- Java - Insecure DeserializationJackson Default Typing