dbcve.org
JobcareerWordPress extension · Chimpgroup

CVE-2024-11284

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 privilege escalation via account takeover in all versions up to, and including, 6.9. This is due to the plugin not properly validating a user's identity prior to updating their password through the account_settings_save_callback() function. This makes it possible for unauthenticated attackers to change arbitrary user's passwords, including administrators, and leverage that to gain access to their account.

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 has a critical privilege escalation vulnerability (CVSS 9.8) in all versions up to 6.9. The account_settings_save_callback() function fails to validate user identity before processing password changes, allowing unauthenticated attackers to reset any user's password including administrator accounts and gain full site access.

MitigationUpdate WP JobHunt to version 6.10 or later immediately. If patching is delayed, disable the plugin or implement web application firewall rules to block unauthorized password reset requests.

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 if WP JobHunt or Jobcareer plugin is installed
    Navigate to WordPress admin > Plugins, or query the wp_options table for option_name = 'active_plugins', or inspect /wp-content/plugins/ directory for 'jobhunt' or 'jobcareer' folder
    Affected if The plugin folder exists and the plugin is active
  2. Identify the installed version number
    Check the plugin main file header (usually plugin.php or includes/plugin-name.php) for 'Version:' tag, or query wp_options for option_name containing 'plugin_version' for jobhunt/jobcareer
    Affected if Version is 6.9 or lower for WP JobHunt, or 7.1 or lower for Jobcareer (Chimpgroup)
  3. Confirm the vulnerable callback function exists in the codebase
    Search plugin files for the function name 'account_settings_save_callback' in the source code
    Affected if The function exists and is registered as a REST API callback (visible in plugin initialization code)
  4. Verify if REST API endpoints are exposed without authentication
    Test accessing the REST API endpoint associated with account_settings_save_callback (typically /wp-json/jobhunt/v1/account_settings or similar) without providing authentication credentials
    Affected if The endpoint responds without requiring valid user authentication

Your environment is affected if the WP JobHunt plugin (or Jobcareer) is installed with version 6.9 or lower (or 7.1 or lower respectively) and the vulnerable callback endpoint is accessible without authentication.

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 WP JobHunt to version 6.10 or later immediately. If patching is delayed, disable the plugin or implement web application firewall rules to block unauthorized password reset requests.

Recommended fix Moderate confidence

WP JobHunt plugin version 7.0 or latest available version (after 6.9)

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate the 'WP JobHunt' plugin in the list.
  4. 4. Check the current installed version of the plugin.
  5. 5. If the installed version is 6.9 or below, update the plugin to the latest available version.
  6. 6. Alternatively, you can update via WordPress Admin > Dashboard > Updates, or manually upload the latest version from wordpress.org.
  7. 7. After updating, verify that the account_settings_save_callback() function has been patched by reviewing plugin changelels or contacting the vendor.
  8. 8. Consider forcing password resets for all administrator accounts as a precautionary measure.

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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