dbcve.org
Jobsearch Wp Job BoardWordPress extension · Eyecix

CVE-2024-43931

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-29
Fix available
A fix is available. Upgrade to 2.5.4 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 allows Object Injection.This issue affects JobSearch: from n/a through 2.5.3.

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.3) allows unauthenticated attackers to inject malicious PHP objects by passing unserialized data, potentially achieving remote code execution through object gadget chains.

MitigationUpgrade to a patched version of JobSearch if available; otherwise, replace unsafe unserialize() calls with json_decode() and implement strict input validation on all user-supplied data before deserialization.

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.4

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. Verify JobSearch plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'JobSearch WP Job Board' or 'eyecix JobSearch' in the list of active plugins
    Affected if The plugin appears in the installed plugins list
  2. Check installed plugin version
    In WordPress admin, click on the JobSearch plugin to view its details, or check the plugin header in /wp-content/plugins/jobsearch/ folder for the 'Version' field
    Affected if Version is 2.5.3 or lower (anything below 2.5.4)
  3. Locate unserialize() calls in plugin code
    Search plugin source files for 'unserialize' pattern - check PHP files in /wp-content/plugins/jobsearch/ directory using grep or file search tools
    Affected if Any unserialize() calls are present that process user-supplied input without validation
  4. Verify plugin is accessible to unauthenticated users
    Confirm the JobSearch plugin endpoints are publicly accessible without authentication - test plugin AJAX handlers or submission forms while logged out
    Affected if Plugin functions accept requests from unauthenticated (logged-out) users

If the JobSearch plugin version is below 2.5.4 and contains unserialize() calls handling user input, the environment is vulnerable to unauthenticated deserialization attacks.

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 2.5.4 or later
Fixed in 2.5.4
Interim mitigation

Upgrade to a patched version of JobSearch if available; otherwise, replace unsafe unserialize() calls with json_decode() and implement strict input validation on all user-supplied data before deserialization.

Recommended fix Moderate confidence

2.5.4

  1. Backup your WordPress site and database before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Find the Jobsearch WP Job Board plugin
  4. If an update is available, click 'Update Now' to upgrade to version 2.5.4
  5. Alternatively, download version 2.5.4 from a trusted source and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version shows 2.5.4 in the plugins list
  7. Test core functionality of the job board to ensure the update did not break existing features

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-43931 — 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-43931 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