LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22497: WordPress Jardi theme <= 1.7.2 - PHP Object Injection vulnerability

Deserialization of Untrusted Data vulnerability in AncoraThemes Jardi jardi allows Object Injection.This issue affects Jardi: from n/a through <= 1.7.2.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-22497 is a critical unsafe deserialization issue in the WordPress Jardi theme through version 1.7.2. A remote unauthenticated attacker could potentially inject malicious PHP objects, risking site compromise. The provided sources do not show active exploitation or name a fixed version.

Executive priority

High priority for any organization running Jardi on public WordPress sites. Start with rapid inventory, then update, disable, or replace affected installations based on vendor guidance. Do not treat this as exploited in the wild unless new evidence appears.

Technical view

The CVE describes CWE-502 deserialization of untrusted data in AncoraThemes Jardi. CVSS 3.1 is 9.8: network exploitable, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact. Public details do not identify the vulnerable endpoint, patch version, or exploit chain.

Likely exposure

Exposure is likely limited to WordPress sites with the Jardi theme installed at version 1.7.2 or earlier. Internet-facing WordPress deployments are highest priority. The CVE metadata says the product default status is unaffected, but the description clearly lists Jardi through 1.7.2 as affected.

Exploitation context

The CVSS vector indicates unauthenticated remote exploitability, but the provided sources do not confirm active exploitation, public exploit code, or CISA KEV listing. PHP object injection impact can vary depending on reachable code paths and available gadget chains, which are not documented in the source bundle.

Researcher notes

Public information is sparse. The CVE establishes unsafe deserialization and critical CVSS characteristics, but not the vulnerable parameter, route, patch, or exploit prerequisites. Validate exposure through asset inventory and version checks, then monitor official advisories for technical detail.

Mitigation direction

  • Inventory WordPress sites for the Jardi theme and its installed version.
  • Prioritize internet-facing sites running Jardi version 1.7.2 or earlier.
  • Check AncoraThemes and Patchstack for a fixed release or official mitigation.
  • If no fix is available, consider disabling or replacing the theme.
  • Ensure recent backups exist before making WordPress theme changes.

Validation and detection

  • Confirm whether Jardi is installed on each WordPress site.
  • Record the exact Jardi theme version and flag versions 1.7.2 or earlier.
  • Check vendor and Patchstack advisories for updated remediation guidance.
  • Review security monitoring for suspicious WordPress activity, without assuming exploitation occurred.
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-22497 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-22497Attack 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
AncoraThemesJardijardi, 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.