Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-52706 – Unauthenticated PHP Object Injection in JetEngine WordPress Plugin <= 3.8.10

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-52706 is a critical unauthenticated PHP Object Injection vulnerability (CWE-502: Deserialization of Untrusted Data) in the JetEngine WordPress plugin by Jetimpex Inc. (Crocoblock), affecting all versions up to and including 3.8.10. With a CVSS v3.1 base score of 9.8, the flaw requires no authentication or user interaction and is exploitable directly over the network, making every internet-exposed WordPress site running a vulnerable version of JetEngine a potential target. A patched version (3.8.10.1) has been released and immediate upgrade is strongly recommended.

Technical details

  • Root cause: The vulnerability stems from improper handling of serialized PHP objects — specifically, the plugin deserializes untrusted, attacker-controlled input without adequate validation, a pattern classified under CWE-502 (Deserialization of Untrusted Data).
  • Trigger conditions: No authentication is required. An unauthenticated remote attacker can send a crafted HTTP request to a vulnerable JetEngine endpoint to inject a malicious PHP object.
  • Attack vector: Network-accessible; low attack complexity, no privileges required, no user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N).
  • Impact: Successful exploitation can enable code injection, SQL injection, path traversal, and denial of service. Where a suitable Property-Oriented Programming (POP) gadget chain is present in the WordPress environment, exploitation can escalate to Remote Code Execution (RCE), resulting in full confidentiality, integrity, and availability compromise (C:H/I:H/A:H).

Affected software

  • JetEngine (WordPress plugin by Jetimpex Inc. / Crocoblock) — all versions <= 3.8.10

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate – Apply the vendor patch: Update JetEngine to version 3.8.10.1 or later. This is the vendor-released fix addressing the deserialization flaw.
  • If patching is not immediately feasible: Restrict public HTTP access to WordPress plugin endpoints at the web server or WAF layer where operationally possible, and consider enabling a virtual patching / firewall rule via your WAF provider to block exploitation attempts until the plugin is updated.
  • Audit for active exploitation: Review web server access logs for anomalous POST requests to JetEngine endpoints, particularly from unexpected source IPs, as a precaution given the zero-interaction nature of this vulnerability.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge