dbcve.org
Jobsearch Wp Job BoardWordPress extension · Eyecix

CVE-2024-47636

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-10
Fix available
A fix is available. Upgrade to after 2.5.9 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Deserialization of Untrusted Data vulnerability in eyecix JobSearch wp-jobsearch allows Object Injection.This issue affects JobSearch: from n/a through <= 2.5.9.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A deserialization vulnerability in the eyecix JobSearch WordPress plugin (versions up to 2.5.9) allows unauthenticated attackers to inject arbitrary PHP objects by supplying malicious serialized data, potentially leading to remote code execution through PHP object injection (POP chain) exploitation.

MitigationUpdate the JobSearch plugin to the latest version which contains a fix for this deserialization vulnerability, or implement input validation to prevent untrusted data from reaching unserialize() calls in the affected code.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jobsearch Wp Job BoardWordPress extension
Affected:<= 2.5.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the JobSearch plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'jobsearch' or similar variant containing the eyecix JobSearch plugin.
    Affected if The plugin folder exists in the WordPress plugins directory.
  2. Determine installed plugin version
    Open the plugin's main PHP file or readme.txt file and locate the Version header or entry. Compare this version number against the affected range (<= 2.5.9).
    Affected if The installed version number is 2.5.9 or lower.
  3. Verify plugin is active
    Check the WordPress database wp_options table for the active_plugins option, or view the Plugins page in WordPress admin to confirm the JobSearch plugin is currently activated.
    Affected if The plugin appears in the list of active plugins.
  4. Identify unserialize() call usage
    Examine the plugin source code for calls to PHP's unserialize() function, particularly those processing data from external sources such as request parameters, POST/GET inputs, or cookies.
    Affected if The plugin code contains unserialize() calls handling unauthenticated user input without prior validation.

The environment is affected if the JobSearch plugin versions 2.5.9 or lower is installed and active, with unserialize() calls present that process untrusted input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.5.9
Interim mitigation

Update the JobSearch plugin to the latest version which contains a fix for this deserialization vulnerability, or implement input validation to prevent untrusted data from reaching unserialize() calls in the affected code.

Recommended fix Moderate confidence

JobSearch wp-jobboard version 2.6.0 or latest available release

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. 3. Locate the JobSearch wp-jobboard plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Verify the update was successful and the plugin is running on a version higher than 2.5.9
  6. 6. Test critical job board functionality (job submissions, applications, user registrations) to ensure the site works correctly
Caveat Review the plugin changelog for version 2.6.0+ to check for any theme/template changes that may require updates to customizations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jobsearch Wp Job Board Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47636 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47636 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data