CVE-2026-42472
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnsafe deserialization vulnerability in MixPHP Framework 2.x thru 2.2.17. The session and cache handlers use unserialize() on data from Redis in the RedisHandler object.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMixPHP Framework 2.x through 2.2.17 contains an unsafe deserialization vulnerability in the RedisHandler object used for session and cache management. The handlers use PHP's unserialize() on data retrieved from Redis without proper validation, allowing an attacker who can control or inject data into Redis to achieve arbitrary PHP object injection and potentially remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm MixPHP Framework installationLocate the MixPHP Framework codebase. Check for a composer.json file with 'mix-php/framework' or look for the 'vendor/mix' directory containing PHP framework files.Affected if MixPHP Framework 2.x is installed and the version is 2.2.17 or lower (check composer.json or version file in the framework root)
-
Identify RedisHandler usageSearch the codebase for references to 'RedisHandler' class or 'redis' session/cache handler configuration. Look in config files (commonly in config/session.php or config/cache.php) and in the vendor/mix directory for handler definitions.Affected if RedisHandler is configured as the session handler or cache driver in the application configuration
-
Verify unsafe unserialize usageOpen the RedisHandler PHP file (typically in vendor/mix/php-file/src/RedisHandler.php or similar path) and search for calls to unserialize() being applied to data retrieved from Redis.Affected if The code contains unserialize() calls on Redis-returned data without prior validation or signature checking
-
Check Redis access controlsReview Redis connection configuration and network access settings. Check if Redis is bound to localhost only or if it allows external connections. Verify if authentication is required.Affected if Redis is accessible from untrusted network sources or lacks proper access controls, allowing an attacker to inject malicious serialized data
-
Determine session/cache data flowTrace how session or cache data flows from Redis to the application. Identify where data is fetched and deserialized in the request lifecycle.Affected if Application directly deserializes session or cache data from Redis without validation at any point in the request flow
If MixPHP Framework 2.x version 2.2.17 or lower is running with RedisHandler enabled and the code uses unserialize() on Redis data without validation, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace unserialize() with json_decode() or implement a safe serialization mechanism, add input validation/signature verification on Redis data before deserialization, and restrict Redis access to trusted sources only.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42472 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-42472 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data