dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-22417

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Deserialization of Untrusted Data vulnerability in ThemeGoods Grand Wedding grandwedding allows Object Injection.This issue affects Grand Wedding: from n/a through < 3.1.11.

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 confidence

Deserialization of untrusted data in the ThemeGoods Grand Wedding WordPress theme allows PHP object injection. Attackers can craft malicious serialized payloads that, when processed by vulnerable deserialization logic, may instantiate arbitrary objects and potentially achieve remote code execution depending on available magic methods.

MitigationUpdate Grand Wedding theme to version 3.1.11 or later which contains the patch for the unsafe deserialization vulnerability.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Grand Wedding theme files
    Check wp-content/themes/ directory for a folder named 'grand-wedding', 'grand-wedding-child', or similar naming convention containing the theme
    Affected if The theme folder exists in the WordPress themes directory
  2. Find theme version number
    Open the style.css file within the Grand Wedding theme folder and look for the 'Version:' declaration in the file header comments
    Affected if Unable to locate version declaration or version number cannot be determined
  3. Compare installed version to fixed version
    Compare the discovered Version number against 3.1.11. Versions lower than 3.1.11 are vulnerable
    Affected if Installed version is below 3.1.11 (for example: 3.1.10, 3.1.9, 3.0.0, etc.)
  4. Verify theme is active
    In WordPress admin dashboard, go to Appearance > Themes to confirm Grand Wedding is the currently active theme
    Affected if Theme is installed but not actively used - still patch as it could be activated at any time

The environment is affected if the Grand Wedding theme is installed with a version number lower than 3.1.11, regardless of whether it is currently active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Grand Wedding theme to version 3.1.11 or later which contains the patch for the unsafe deserialization vulnerability.

Recommended fix High confidence

Grand Wedding theme version 3.1.11 or later

  1. 1. Backup your WordPress site before making any changes.
  2. 2. Navigate to your WordPress dashboard and go to Appearance > Themes.
  3. 3. Locate the Grand Wedding theme in your installed themes.
  4. 4. Check the current version of the Grand Wedding theme to confirm it is below 3.1.11.
  5. 5. If an update is available, click to update the theme to the latest version (3.1.11 or later).
  6. 6. If no update appears in WordPress, download the latest version from ThemeGoods official source or WordPress theme repository and upload/install it.
  7. 7. Verify the theme has been updated to version 3.1.11 or later.
  8. 8. Test critical site functionality after the update to ensure compatibility.
Caveat Review theme changelog for any styling or feature changes that may require template adjustments after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22417 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22417 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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