Code execution via unchecked file deserialization
Published May 1, 2026 · Updated May 1, 2026
Unsafe deserialization in MixPHP Framework 2.x through 2.2.17 allows attackers to execute code through poisoned cache or session files. FileHandler reads serialized data from filesystem-backed session and cache storage and passes the bytes to PHP unserialize() without an integrity check or class allowlist. Reaching the sink requires the ability to create or alter a stored file; successful exploitation runs PHP code with the application process privileges.
Summary
What happened
Unsafe deserialization in MixPHP Framework 2.x through 2.2.17 allows attackers to execute code through poisoned cache or session files. FileHandler reads serialized data from filesystem-backed session and cache storage and passes the bytes to PHP unserialize() without an integrity check or class allowlist. Reaching the sink requires the ability to create or alter a stored file; successful exploitation runs PHP code with the application process privileges.
The record
- CVE
- CVE-2026-42473
- Published
- May 1, 2026
- Updated
- May 1, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-502
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- May 1, 2026CVE publishedPublication date reported by the CVE source.
- May 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo