# CVE-2025-7374: WP JobHunt <= 7.6 Authenticated (Custom+) Authorization Bypass

> Authenticated attackers with Candidate or Employer roles can bypass login restrictions to access inactive or pending accounts in the WP JobHunt plugin.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-3rfp-m78p-qcfp

## What is CVE-2025-7374?

CVE-2025-7374 is a medium-severity authentication bypass vulnerability in WP JobHunt, published on 10 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP JobHunt plugin for WordPress, used by the JobCareer theme, is vulnerable to authorization bypass in all versions up to, and including, 7.6. This is due to insufficient login restrictions on inactive and pending accounts. This makes it possible for authenticated attackers, with Candidate- and Employer-level access and above, to log in to the site even if their account is inactive or pending.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-7374?


## How do I fix CVE-2025-7374?

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

## Is CVE-2025-7374 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7374 and fix it if it is affected.

What it is: CVE-2025-7374 is a medium-severity authentication bypass vulnerability in WP JobHunt, published on 10 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-7374 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-2025-7374/ (Markdown: https://insights.sbomify.com/CVE-2025-7374/index.md)
```

## Sources

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

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