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

New CVE Detected

CVE-2026-84834 – Unauthenticated PHP Object Injection – EyeCix JobSearch WordPress Plugin ≤ 3.2.0

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

Summary

CVE-2026-84834 is a critical, unauthenticated PHP Object Injection vulnerability (CWE-502, Deserialization of Untrusted Data) affecting the EyeCix Technologies JobSearch WordPress plugin in versions up to and including 3.2.0. The flaw allows remote, unauthenticated attackers to submit crafted serialized data that the plugin deserializes, with a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: The plugin deserializes attacker-controlled input without adequate validation, enabling PHP Object Injection (CAPEC-586).
  • Trigger conditions: No authentication or user interaction is required; an attacker only needs network access to a vulnerable JobSearch installation.
  • Attack vector: Network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N).
  • Impact: If a usable "POP chain" (a sequence of existing classes/methods that can be chained during deserialization) is present in the WordPress environment, exploitation can lead to arbitrary file operations, data manipulation, or remote code execution, in addition to the direct impact reflected in the CVSS score of full confidentiality, integrity, and availability loss.

Affected software

  • EyeCix Technologies JobSearch WordPress plugin, versions ≤ 3.2.0

Severity

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

Mitigation and recommended actions

  • Immediate: No fixed version has been publicly confirmed for this CVE as of publication. Site owners should check for and apply the latest available JobSearch plugin update from the vendor as soon as one addressing this issue is released.
  • If no patch is available: Restrict or disable public access to the JobSearch plugin’s exposed endpoints where feasible, deploy a web application firewall rule to block requests containing serialized PHP object payloads, and monitor logs for anomalous POST data. Consider temporarily deactivating the plugin on internet-facing WordPress sites until a fix is confirmed and applied.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: /wp-content/plugins/wp-jobsearch/

References

Are you exposed?

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge