CVE-2026-32355: PHP Object Injection in JetEngine
Platform
wordpress
Component
jet-engine
Fixed in
3.8.4.1
CVE-2026-32355 describes a PHP Object Injection vulnerability affecting the JetEngine plugin for WordPress. This vulnerability allows authenticated attackers with Contributor-level access or higher to inject a PHP Object into the system. While the JetEngine plugin itself lacks a known PHP Object Poisoning (POP) chain, the vulnerability's impact significantly increases if other plugins or themes on the WordPress site contain such a chain, potentially leading to remote code execution.
Detect this CVE in your project
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Impact and Attack Scenarios
The core risk lies in the potential for Remote Code Execution (RCE). While CVE-2026-32355 doesn't directly enable RCE, it provides the entry point for an attacker to inject malicious code. If another plugin or theme on the WordPress site is vulnerable to PHP Object Poisoning (POP), the injected object can be exploited to trigger the POP chain, granting the attacker control over the server. This could lead to data breaches, website defacement, malware installation, and complete system compromise. The blast radius extends to any sensitive data stored on the WordPress site, including user credentials, customer information, and financial data.
Exploitation Context
CVE-2026-32355 was published on February 14, 2026. Its severity is currently assessed as HIGH (CVSS 7.5). No public Proof-of-Concept (POC) exploits have been publicly disclosed as of this writing. The vulnerability's exploitation depends on the presence of a POP chain in other installed plugins or themes, which introduces a dependency and potentially limits immediate exploitation. No known active campaigns targeting this specific vulnerability have been reported.
Threat Intelligence
Exploit Status
EPSS
0.05% (17% percentile)
CVSS Vector
What do these metrics mean?
- Attack Vector
- Network — remotely exploitable over the internet. No physical or local access required. Widest attack surface.
- Attack Complexity
- High — requires a race condition, non-default configuration, or specific circumstances. Harder to exploit reliably.
- Privileges Required
- Low — any valid user account is sufficient. Basic authenticated access required.
- User Interaction
- None — attack is automatic and silent. Victim does nothing: no click, no file open.
- Scope
- Unchanged — impact is limited to the vulnerable component itself.
- Confidentiality
- High — complete confidentiality loss. Attacker can read all data: credentials, keys, personal data.
- Integrity
- High — attacker can write, modify, or delete any data: databases, config files, or code.
- Availability
- High — complete crash or resource exhaustion. Full denial of service.
Affected Software
Weakness Classification (CWE)
Timeline
- Reserved
- Published
- Modified
- EPSS updated
Mitigation and Workarounds
The primary mitigation is to immediately upgrade JetEngine to version 3.8.4.1 or later. If upgrading is not feasible due to compatibility issues or breaking changes, consider temporarily disabling the JetEngine plugin as a workaround. Web Application Firewalls (WAFs) configured to detect and block deserialization of untrusted input can provide an additional layer of protection. Monitor WordPress logs for suspicious deserialization attempts, specifically targeting JetEngine functionality. Regularly scan WordPress plugins and themes for known vulnerabilities using a reputable security scanner.
How to fix
Update to version 3.8.4.1, or a newer patched version
Frequently asked questions
What is CVE-2026-32355 — PHP Object Injection in JetEngine?
CVE-2026-32355 is a HIGH severity vulnerability in the JetEngine WordPress plugin allowing authenticated attackers to inject PHP Objects. Exploitation requires a PHP Object Poisoning (POP) chain in another plugin or theme, potentially leading to RCE.
Am I affected by CVE-2026-32355 in JetEngine?
You are affected if you are using JetEngine version 3.8.4.1 or earlier. Check your plugin version using wp plugin list and upgrade immediately if vulnerable.
How do I fix CVE-2026-32355 in JetEngine?
Upgrade JetEngine to version 3.8.4.1 or later. If upgrading is not possible, temporarily disable the plugin. Consider WAF rules to block deserialization attempts.
Is CVE-2026-32355 being actively exploited?
No active campaigns targeting CVE-2026-32355 have been publicly reported, but exploitation is possible if a POP chain exists on the system.
Where can I find the official JetEngine advisory for CVE-2026-32355?
Refer to the official JetEngine website and WordPress plugin repository for updates and security advisories related to CVE-2026-32355.
Is your project affected?
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Detect this CVE in your project
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Scan your WordPress project now — no account
Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.
Drag & drop your dependency file
composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...