# CVE-2024-11284: WP JobHunt <= 7.1 - Unauthenticated Privilege Escalation via Password Reset/Account Takeover

> Unauthenticated attackers can change arbitrary user passwords, including administrators, leading to account takeover and privilege escalation in WP JobHunt.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Mar 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-jh23-v8pg-3gxq

## What is CVE-2024-11284?

CVE-2024-11284 is a critical authentication bypass vulnerability in WP JobHunt, published on 14 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2024-11284?

It affects 1 product.


Products: Chimpgroup Jobcareer.

## How do I fix CVE-2024-11284?

No fix has been published for CVE-2024-11284 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-11284 being exploited?

There is no known exploitation of CVE-2024-11284 in the wild and no public exploit code.

## Other vulnerabilities in WP JobHunt

- [CVE-2024-11285](https://insights.sbomify.com/CVE-2024-11285/): WP JobHunt <= 7.1 - Unauthenticated Privilege Escalation via Email Update/Account Takeover (critical 9.8)
- [CVE-2024-11286](https://insights.sbomify.com/CVE-2024-11286/): WP JobHunt <= 7.1 - Authentication Bypass (critical 9.8)
- [CVE-2024-12810](https://insights.sbomify.com/CVE-2024-12810/): Missing authorization in JobCareer | Job Board Responsive WordPress Theme (high 8.8)
- [CVE-2024-11283](https://insights.sbomify.com/CVE-2024-11283/): WP JobHunt <= 7.1 - Authentication Bypass to Candidate (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11284 and fix it if it is affected.

What it is: CVE-2024-11284 is a critical authentication bypass vulnerability in WP JobHunt, published on 14 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-11284 in the wild and no public exploit code.

Affected product: WP JobHunt. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-11284/ (Markdown: https://insights.sbomify.com/CVE-2024-11284/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-11284
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-11284
- OSV: https://osv.dev/vulnerability/CVE-2024-11284

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-11284/
Summaries are generated and may contain mistakes; the official description above is the record.