LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22475: WordPress Estate theme <= 1.3.4 - PHP Object Injection vulnerability

Deserialization of Untrusted Data vulnerability in axiomthemes Estate estate allows Object Injection.This issue affects Estate: from n/a through <= 1.3.4.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-22475 is a critical vulnerability in the WordPress Estate theme by axiomthemes, affecting versions up to 1.3.4. A remote, unauthenticated attacker may be able to trigger PHP object injection through unsafe deserialization. For organizations using this theme, treat it as urgent because the CVSS rating indicates potential full confidentiality, integrity, and availability impact.

Executive priority

High priority for any organization running the Estate WordPress theme. The vulnerability is critical and potentially remotely exploitable without login, but public evidence provided does not confirm active exploitation or identify a fixed version.

Technical view

The CVE describes CWE-502, deserialization of untrusted data, in Estate theme <= 1.3.4. The CVSS 3.1 vector is 9.8: network-accessible, low complexity, no privileges, no user interaction, unchanged scope, with high CIA impact. Public sources do not name a fixed version or detailed vendor mitigation.

Likely exposure

Exposure is limited to WordPress sites with the axiomthemes Estate theme installed at version 1.3.4 or earlier. Public sources do not clarify whether inactive installations are exploitable, so include all installed copies in review.

Exploitation context

The CVSS vector indicates unauthenticated remote exploitability without user interaction. The provided sources do not state active exploitation, and the CVE is not listed as KEV in the supplied data.

Researcher notes

Analysis is constrained to the CVE record and Patchstack entry. No exploit details, proof-of-concept status, or vendor patch version are provided in the source bundle. Avoid assuming exploitability on non-Estate themes or unsupported version ranges.

Mitigation direction

  • Inventory WordPress sites for the Estate theme and record installed versions.
  • Prioritize any Estate installation at version 1.3.4 or earlier.
  • Check Patchstack and vendor guidance for a fixed release or official workaround.
  • Update to a fixed version if one is confirmed by trusted sources.
  • If no fix is available, consider removing or replacing the theme.

Validation and detection

  • Confirm the theme slug/name is Estate by axiomthemes.
  • Verify the installed theme version on each WordPress site.
  • Check whether vulnerable copies exist in production, staging, or backups.
  • Review Patchstack and CVE records for updated remediation information.
  • Monitor logs for unusual activity, without assuming compromise from this CVE alone.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22475 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-22475Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
axiomthemesEstateestate, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.