JobcareerWordPress extension · Chimpgroup
CVE-2024-11285
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 · uneditedThe WP JobHunt plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 7.1. This is due to the plugin not properly validating a user's identity prior to updating their details like email via the account_settings_callback() function. This makes it possible for unauthenticated attackers to change arbitrary user's email addresses, including administrators, and leverage that to reset the user's password and 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 confidenceThe WP JobHunt plugin for WordPress contains an unauthenticated privilege escalation vulnerability in versions up to 7.1. The account_settings_callback() function fails to validate user identity before allowing email address changes, enabling unauthenticated attackers to modify any user's email including administrators and reset their passwords for full account takeover.
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
<= 7.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify the WP JobHunt plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP JobHunt' or 'Jobcareer' or 'Chimpgroup Jobcareer'. Also check the wp-content/plugins/ directory for folders named 'jobhunt', 'jobcareer', or similar.Affected if The plugin is present and active in the WordPress installation
-
Check the installed plugin versionIn the WordPress plugin list, click on the plugin to view details, or inspect the plugin's main PHP file for a version constant, or check the readme.txt file in the plugin directory for the 'Stable tag' or 'Version' field.Affected if The version is 7.1 or any version lower than 7.1 (the vulnerable version range)
-
Confirm the vulnerable endpoint is accessibleTest if the WordPress AJAX endpoint /wp-admin/admin-ajax.php is reachable and check if the 'account_settings_callback' action is registered and callable without authentication. This can be done by inspecting the plugin's code for add_action calls with 'wp_ajax_account_settings_callback' or 'wp_ajax_nopriv_account_settings_callback'.Affected if The account_settings_callback function is hooked to an AJAX or REST endpoint accessible to unauthenticated users (wp_ajax_nopriv_ or public REST route)
-
Verify user capability checks are missingExamine the plugin source code for the account_settings_callback function. Look for checks like current_user_can(), is_user_logged_in(), or similar authorization logic before allowing email modifications.Affected if The function lacks proper user authentication or capability verification before processing account settings changes
You are affected if the WP JobHunt/Jobcareer plugin version 7.1 or lower is installed and active, and the account_settings_callback endpoint is accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to the patched version of WP JobHunt when available. If no patch exists, disable the plugin or implement web application firewall rules to block unauthorized account modification requests until a fix is released.
Fix this in Jobcareer
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11285 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-11285 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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