CVE-2026-32355

JetEngine < 3.8.4.1 - Authenticated (Contributor+) PHP Object Injection

2026-02-14 00:00
Phat RiO

Strategic Overview

Status
Patched in 3.8.4.1
Affected Plugin
JetEngine
Affected Version
< 3.8.4.1
CVSS
7.5High
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE-2026-32355
View all JetEngine vulnerabilities

At a glance

CVE-2026-32355 is a high-severity Deserialization of Untrusted Data vulnerability in the JetEngine WordPress plugin, affecting versions < 3.8.4.1. It carries a CVSS score of 7.5 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.8.4.1; sites on affected versions should update now. Disclosed February 2026, reported by Phat RiO.

Vulnerability Overview

The JetEngine plugin for WordPress is vulnerable to PHP Object Injection in all versions up to 3.8.4.1 (exclusive) via deserialization of untrusted input. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-502: Deserialization of Untrusted Data

Reaching this weakness in JetEngine < 3.8.4.1 takes an account at Contributor level or above. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.

A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For JetEngine the fix is 3.8.4.1: builds < 3.8.4.1 are affected, anything from 3.8.4.1 onward is not.

Remediation

Update to version 3.8.4.1, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: JetEngine 3.8.4.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C