dbcve.org
JobcareerWordPress extension · Chimpgroup

CVE-2024-11283

HIGH · 7.5 CVSS v3.1 Published 2025-03-14
Fix available
A fix is available. Upgrade to after 7.1 or later.
See remediation →
84/100
Remediation priority · High
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 wp_ajax_google_api_login_callback function not properly verifying a user's identity prior to authenticating them. This makes it possible for unauthenticated attackers to access arbitrary candidate accounts.

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 WordPress plugin up to version 7.1 contains an authentication bypass vulnerability in the wp_ajax_google_api_login_callback function. This function fails to properly verify user identity before authenticating, allowing unauthenticated attackers to access arbitrary candidate accounts by manipulating the Google API login callback.

MitigationUpdate WP JobHunt plugin to version 7.2 or later. If immediate update is not possible, consider restricting access to the affected AJAX endpoint via web server configuration or temporarily disabling the plugin.

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
None
Availability
None

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

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. Identify plugin installation and version
    Check the installed version of WP JobHunt (Jobcareer) plugin via WordPress admin dashboard under Plugins > Installed Plugins, or inspect the plugin header in wp-content/plugins/jobhunt/functions.php for the version constant.
    Affected if Installed version is 7.1 or lower.
  2. Verify Google API login feature is active
    Navigate to WordPress admin > Jobhunt Settings > Candidate Options > Google Login Settings, or inspect the plugin configuration database entries for google_login_module option.
    Affected if Google Login feature is enabled in the plugin settings.
  3. Confirm vulnerable AJAX endpoint exists
    Check if the file containing wp_ajax_google_api_login_callback exists by searching for the function definition in plugin files (typically in includes/admin/callbacks/ or similar), or test access to /wp-admin/admin-ajax.php?action=google_api_login_callback.
    Affected if The AJAX callback function is present in the plugin code and responds to requests.
  4. Inspect authentication logic in callback
    Examine the wp_ajax_google_api_login_callback function code for missing user verification - look for direct user authentication without proper token validation or user ID verification before wp_set_auth_cookie or wp_signon calls.
    Affected if The code authenticates users without validating the Google API response or verifying the user identity matches the provided credentials.

User is affected if WP JobHunt/Jobcareer plugin version is 7.1 or lower AND the Google Login feature is enabled, exposing the unauthenticated AJAX callback.

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.

From vendor data
Upgrade available Upgrade to a release after 7.1
Interim mitigation

Update WP JobHunt plugin to version 7.2 or later. If immediate update is not possible, consider restricting access to the affected AJAX endpoint via web server configuration or temporarily disabling the plugin.

Fix this in Jobcareer Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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