dbcve.org
JobcareerWordPress extension · Chimpgroup

CVE-2024-11286

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-14
Fix available
A fix is available. Upgrade to after 7.1 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
The WP JobHunt plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 7.1. This is due to the plugin not properly verifying a user's identity prior to authenticating them through the cs_parse_request() function. This makes it possible for unauthenticated attackers to to log in to any user's account, including administrators.

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 · high confidence

The WP JobHunt plugin for WordPress versions up to 7.1 contains an authentication bypass vulnerability in the cs_parse_request() function. This function fails to properly verify a user's identity before authenticating them, allowing unauthenticated attackers to log in as any user account, including administrators, by manipulating the authentication flow.

MitigationUpdate the WP JobHunt plugin to version 7.2 or later. If no patched version is available, disable the plugin immediately and consider alternative job listing solutions.

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
JobcareerWordPress extension
Affected:<= 7.1

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. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'WP JobHunt' or 'Jobcareer' by Chimpgroup. Note the version number displayed. Alternatively, inspect the plugin main file header in wp-content/plugins/jobhunt/jobhunt.php or similar path.
    Affected if The displayed version is 7.1 or lower, or if no version is shown but the plugin filename indicates an older release.
  2. Confirm plugin is active
    Verify that the WP JobHunt / Jobcareer plugin is currently activated in the WordPress site. Check the Plugins screen status column.
    Affected if The plugin shows as 'Active' in the WordPress plugins list.
  3. Locate the cs_parse_request function
    Access the site files via FTP or file manager. Search the plugin directory (wp-content/plugins/jobhunt/) for the file containing the cs_parse_request function. Common locations include includes/cs_core_files.php or similar include files.
    Affected if The file containing cs_parse_request exists in the active plugin installation.
  4. Inspect authentication logic in cs_parse_request
    Open the file containing cs_parse_request and examine the function code. Look for the request authentication section where user identity should be verified. Check for missing or inadequate user verification before authentication logic executes.
    Affected if The function lacks proper user identity verification or contains conditional checks that can be bypassed before authentication occurs.

If the plugin version is 7.1 or lower, the plugin is active, and the cs_parse_request function exists with insufficient authentication checks, the environment is affected by this CVE.

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 7.1
Interim mitigation

Update the WP JobHunt plugin to version 7.2 or later. If no patched version is available, disable the plugin immediately and consider alternative job listing solutions.

Recommended fix Moderate confidence

Version 7.2 or later (check WordPress repository or theme developer for the specific fixed release)

  1. Check the WP JobHunt plugin or Jobcareer theme for an available update in the WordPress admin dashboard under Updates or Plugins > All Plugins
  2. If an update to version 7.2 or higher is available, update the plugin/theme immediately
  3. After updating, verify that the cs_parse_request() function has been patched by reviewing the plugin changelog or release notes
  4. Ensure all administrator accounts are using strong, unique passwords as a secondary security measure
  5. Review user accounts for any unauthorized access or newly created administrator accounts
Caveat Review plugin/theme changelog for any compatibility notes with your WordPress version or other installed plugins

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

Fix this in Jobcareer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11286 — 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-11286 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