dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-23542

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-19
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 Restaurant grandrestaurant allows Object Injection.This issue affects Grand Restaurant: from n/a through <= 7.0.10.

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

A deserialization vulnerability in the ThemeGoods Grand Restaurant WordPress theme allows remote attackers to inject malicious PHP objects by supplying untrusted data to vulnerable unserialize() calls. This Object Injection can enable remote code execution, file operations, or SQL injection attacks via property-oriented programming (POP) chains, depending on available classes in the application.

MitigationUpdate the Grand Restaurant theme to version 7.0.11 or later which contains the patch; if immediate patching is not possible, disable the theme or deploy a WAF rule to block requests to the vulnerable endpoint.

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. Identify if Grand Restaurant theme is installed
    Navigate to wp-content/themes/ and look for a folder named 'grand-restaurant' or similar. Check for style.css file in the theme directory.
    Affected if The theme folder exists on the WordPress installation.
  2. Determine the installed theme version
    Open the theme's style.css file (usually at /wp-content/themes/grand-restaurant/style.css) and locate the 'Version:' comment in the file header.
    Affected if The version number displayed is below 7.0.11.
  3. Check for unsafe unserialize() calls in theme code
    Use a file search or grep tool to scan PHP files in the theme directory for 'unserialize(' patterns, particularly in files that handle request parameters or AJAX endpoints.
    Affected if Files contain unserialize() calls that process input from $_GET, $_POST, or $_REQUEST without sanitization.
  4. Verify if user-controlled data reaches the unserialize call
    Examine the code flow around any found unserialize() calls to determine if parameters from URL query strings, form submissions, or cookies are passed directly to the unserialize function.
    Affected if User-supplied data from request parameters flows into the unserialize() function without validation.

A user is affected if the Grand Restaurant theme is installed with a version lower than 7.0.11 AND the theme contains unserialize() calls that process untrusted user input.

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 the Grand Restaurant theme to version 7.0.11 or later which contains the patch; if immediate patching is not possible, disable the theme or deploy a WAF rule to block requests to the vulnerable endpoint.

Recommended fix Moderate confidence

Latest version of Grand Restaurant theme (newer than 7.0.10) - contact ThemeGoods for the exact fixed release

  1. 1. Backup your WordPress site before making any changes
  2. 2. Update the Grand Restaurant theme to the latest available version from ThemeGoods or your WordPress theme repository
  3. 3. Verify the update was successful by checking the theme version in Appearance > Themes
  4. 4. Test critical functionality on your site to ensure the update did not break existing features
  5. 5. Monitor for any unusual behavior or errors after the update
Caveat Review theme changelog for any template or feature changes that may require adjustments after upgrading

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 / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23542 — 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-23542 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