dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-32355

HIGH · 8.8 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Crocoblock JetEngine jet-engine allows Object Injection.This issue affects JetEngine: from n/a through < 3.8.4.1.

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 JetEngine WordPress plugin allows attackers to inject serialized PHP objects by supplying malicious data to vulnerable deserialization functions, potentially leading to code execution or other injection attacks.

MitigationUpdate JetEngine to version 3.8.4.1 or later. Until then, restrict access to any JetEngine-related AJAX endpoints or admin functions that handle serialized data input.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify JetEngine plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for JetEngine, or check the /wp-content/plugins/jet-engine directory exists
    Affected if JetEngine plugin is present in the WordPress installation
  2. Check installed JetEngine version
    In WordPress admin > Plugins > Installed Plugins > JetEngine, read the version number displayed below the plugin name
    Affected if Version is lower than 3.8.4.1 (vulnerable); version 3.8.4.1 or later is patched
  3. Identify exposed JetEngine AJAX endpoints
    Inspect site for AJAX handlers at /wp-admin/admin-ajax.php?action=jet_engine_* or public endpoints with jet_engine in the URL path
    Affected if Any JetEngine AJAX endpoints are accessible to unauthenticated or low-privileged users
  4. Verify serialized data handling is active
    Check if any JetEngine dynamic content, custom post types, or dynamic fields are configured to accept user input that could reach deserialization functions
    Affected if JetEngine features that process serialized or object-type data are enabled and publicly accessible

You are affected if JetEngine plugin is installed with a version lower than 3.8.4.1 and any AJAX endpoints or features handling serialized data are exposed to users.

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 JetEngine to version 3.8.4.1 or later. Until then, restrict access to any JetEngine-related AJAX endpoints or admin functions that handle serialized data input.

Recommended fix Moderate confidence

JetEngine 3.8.4.1

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find JetEngine in the plugin list
  4. Check if an update to version 3.8.4.1 or newer is available
  5. If update available, click 'Update Now' to upgrade to version 3.8.4.1
  6. If no update shown, deactivate and delete the current JetEngine plugin, then reinstall version 3.8.4.1 or latest version from WordPress repository or Crocoblock
  7. After update, verify the plugin version is 3.8.4.1 or later

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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