Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-28074

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 ThemeREX Pizza House pizzahouse allows Object Injection.This issue affects Pizza House: from n/a through <= 1.4.0.

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 confidence

A deserialization of untrusted data vulnerability in the ThemeREX Pizza House WordPress theme allows unauthenticated attackers to inject malicious PHP objects, potentially leading to remote code execution. The vulnerability stems from insecure use of PHP's unserialize() function on user-controlled input.

MitigationUpdate the Pizza House theme to a patched version if available, or replace with a secure theme. If immediate patching is unavailable, disable the theme and monitor for compromise indicators.

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. Confirm Pizza House theme is installed
    In WordPress admin, go to Appearance > Themes and check if the Pizza House theme by ThemeREX is active or installed. Alternatively, check the /wp-content/themes/ directory for a folder named 'pizza-house' or similar.
    Affected if The Pizza House theme by ThemeREX is installed and active
  2. Identify the theme version
    Check the style.css file in the theme folder for the 'Version:' header, or look in the theme's main PHP file for a version constant. Compare this to the patched version once available.
    Affected if The installed version is older than the patched version
  3. Locate the vulnerable unserialize call
    Search theme PHP files for 'unserialize' calls that process $_GET, $_POST, $_REQUEST, or file input without sanitization. Look for patterns like 'unserialize($_REQUEST[...])' or similar user-input deserialization.
    Affected if Code contains unserialize() applied directly to user-controlled parameters without validation
  4. Check for exposed vulnerable endpoints
    Review theme files for AJAX handlers or direct access points that accept serialized data. Test if theme-specific URLs (often under /wp-admin/admin-ajax.php or theme-specific endpoints) accept and process serialized input.
    Affected if The vulnerable deserialization endpoint is accessible without authentication
  5. Monitor for exploitation attempts
    Review web server access logs and WordPress debug logs for requests containing serialized PHP objects (look for 'O:' patterns or base64-encoded serialized strings) to theme endpoints.
    Affected if Suspicious serialized payloads are being sent to the site
  6. Check for post-exploitation indicators
    Look for newly created PHP files in the theme directory or wp-content/uploads/ that contain suspicious code, eval() calls, or base64_decode() patterns indicating webshell installation.
    Affected if Unknown malicious files or code patterns exist in the theme or upload directories

You are affected if the ThemeREX Pizza House theme is installed and its version predates the patched version, or if the vulnerable unserialize() call on user input is present and accessible.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Pizza House theme to a patched version if available, or replace with a secure theme. If immediate patching is unavailable, disable the theme and monitor for compromise indicators.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28074 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