CVE-2026-22475
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 · uneditedDeserialization of Untrusted Data vulnerability in axiomthemes Estate estate allows Object Injection.This issue affects Estate: from n/a through <= 1.3.4.
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 · moderate confidenceThis is a PHP Object Injection vulnerability in the Estate WordPress theme caused by insecure use of PHP's unserialize() function on untrusted input. Attackers can craft malicious serialized PHP objects to achieve remote code execution, potentially compromise the entire WordPress installation, or perform other attacks like file operations. The vulnerability affects all versions up to and including 1.3.4.
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 Estate theme installationCheck the wp-content/themes/estate directory exists on your WordPress serverAffected if The Estate theme directory is present in the WordPress themes folder
-
Identify the installed theme versionOpen the style.css file in wp-content/themes/estate/ and look for the 'Version:' header in the file commentsAffected if The version listed is 1.3.4 or lower, or if no version is explicitly stated but the theme is present
-
Locate insecure unserialize() callsSearch all PHP files in the theme directory for 'unserialize(' patterns, particularly in files that handle user input or request parametersAffected if Any PHP file in the theme contains an unserialize() call processing data from $_GET, $_POST, $_REQUEST, or similar user-controlled sources
-
Verify user input reaches unserialize()Examine the code around any found unserialize() calls to trace whether parameters from HTTP requests (GET, POST, cookies, or other request data) are passed to the unserialize() functionAffected if User-controlled data from HTTP requests is directly or indirectly fed to an unserialize() function call
You are affected if the Estate WordPress theme is installed with version 1.3.4 or lower and contains unserialize() calls that process untrusted HTTP request parameters.
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 unsafe unserialize() calls with secure alternatives like json_decode(), implement strict allowlist validation on any user-controlled data before deserialization, and audit all data handling code paths for similar issues.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22475 — 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-22475 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