dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-49075

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-17
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
Contributor PHP Object Injection in JetEngine <= 3.8.9.1 versions.

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 PHP Object Injection vulnerability in JetEngine plugin versions 3.8.9.1 and below allows attackers with Contributor-level access to inject malicious PHP objects via unserialized user input, potentially leading to remote code execution through property-oriented programming (POP) chains.

MitigationUpgrade JetEngine to the latest version. If patching is not immediately possible, disable or restrict Contributor-level user registrations and audit the codebase for unsafe unserialize() calls on user-supplied data.

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. 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 on the server
    Affected if JetEngine plugin is not installed on the WordPress site
  2. Check installed JetEngine version
    In WordPress admin, go to Plugins > Installed Plugins and locate JetEngine; the version number is displayed below the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/jet-engine/jet-engine.php for the Version field
    Affected if The version number is 3.8.9.1 or lower, or cannot be determined (plugin is outdated)
  3. Confirm Contributor-level user accounts exist
    In WordPress admin, go to Users > All Users and review the Role column for any accounts assigned the Contributor role
    Affected if At least one user with Contributor role exists on the site
  4. Inspect for unsafe unserialize usage in JetEngine code
    Search the JetEngine plugin directory for unserialize() calls that process user input: use grep or a file search to find 'unserialize' in PHP files within /wp-content/plugins/jet-engine/, then verify if any of these calls handle data from $_POST, $_GET, $_REQUEST, or user meta/custom fields
    Affected if The JetEngine plugin contains unserialize() calls that process user-supplied input without prior validation

You are affected if JetEngine version 3.8.9.1 or lower is installed AND Contributor-level users exist AND the plugin uses unserialize on 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

Upgrade JetEngine to the latest version. If patching is not immediately possible, disable or restrict Contributor-level user registrations and audit the codebase for unsafe unserialize() calls on user-supplied data.

Recommended fix Moderate confidence

Latest version of JetEngine beyond 3.8.9.1 (confirm fixed version from vendor release notes)

  1. 1. Identify the current installed version of JetEngine plugin in your WordPress environment
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. If JetEngine version is 3.8.9.1 or lower, update to the latest available version from the WordPress plugin repository or Crocoblock
  4. 4. After updating, verify the new version number confirms the update was successful
  5. 5. Test critical JetEngine functionality (Dynamic Content, Listings, Modules) to ensure the update did not break existing functionality
  6. 6. Review JetEngine/Crocoblock release notes or patchstack.com for the specific fixed version number
Caveat Minor/major version upgrade may introduce template/setting changes - review changelog before production deployment

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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