Security readout for executives and security teams
Plain-English summary
JobSearch for WordPress is reported vulnerable through version 3.2.0. An unauthenticated internet user may trigger unsafe PHP object handling, potentially compromising site data, integrity, or availability. The supplied sources rate it CVSS 9.8, but do not document active exploitation or a confirmed fixed version.
Executive priority
Treat this as an urgent remediation item for internet-facing WordPress systems. Immediately establish whether JobSearch is deployed and reduce exposure. Escalate suspected compromise for incident response, while recognizing that active exploitation and a confirmed patched release are not established by the supplied evidence.
Technical view
CVE-2026-84834 is classified as CWE-502, PHP object injection through deserialization of untrusted data. The reported attack requires network access, no credentials, and no user interaction. Confidentiality, integrity, and availability impacts are rated high. Actual outcomes may depend on available PHP object chains and application context; the bundle does not establish a specific execution path.
Likely exposure
Internet-facing WordPress sites running the JobSearch plugin version 3.2.0 or earlier are the stated exposure group. Confirmed scope is uncertain because the CVE description names those versions while the supplied structured affected record lists no version and defaults to unaffected.
Exploitation context
The CVSS vector indicates low-complexity, unauthenticated remote exploitation without user interaction. However, the CVE is not listed as KEV in the supplied bundle, and no supplied source confirms exploitation in the wild, public exploit availability, or a demonstrated impact chain.
Researcher notes
The record supports unauthenticated CWE-502 exposure and a 9.8 CVSS score, but provides no vulnerable endpoint, root cause detail, gadget-chain evidence, exploit telemetry, or named fixed release. Version metadata is internally inconsistent: narrative scope says through 3.2.0, while the structured affected entry supplies no version and defaults to unaffected.
Mitigation direction
- Inventory WordPress sites and identify installed JobSearch versions.
- Disable or remove affected versions where business operations permit.
- Restrict public access to affected sites if immediate removal is impractical.
- Check the vendor and Patchstack guidance for a confirmed fixed version.
- Prioritize backups and incident monitoring until remediation is verified.
Validation and detection
- Confirm whether JobSearch is installed, active, and version 3.2.0 or earlier.
- Verify affected instances are disabled, removed, isolated, or updated according to authoritative guidance.
- Review web and application logs for unusual unauthenticated requests around the plugin.
- Check WordPress files, accounts, settings, and scheduled tasks for unauthorized changes.
- Reassess version scope when the CVE record or vendor advisory is clarified.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-84834 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/wordpress/plugin/wp-jobsearch/vulnerability/wordpress-jobsearch-plugin-3-2-0-php-object-injection-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.