CVE-2025-7374
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, 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.
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 fails to properly validate account status during authentication, allowing users with Candidate or Employer roles whose accounts are inactive or pending to bypass login restrictions and gain unauthorized access to the site.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP JobHunt plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP JobHunt' or 'JobHunt' in the list. Alternatively, check the /wp-content/plugins/ directory for a jobhunt folder.Affected if WP JobHunt plugin is present on the WordPress site
-
Check installed WP JobHunt versionIn WordPress admin, go to Plugins > Installed Plugins and locate the WP JobHunt plugin to view its version number, or inspect the main plugin file header for the 'Version' tag.Affected if Version is 7.6 or lower (the vulnerability affects versions up to 7.6)
-
Identify Candidate and Employer role usersIn WordPress admin, go to Users and filter by role to find accounts with 'Candidate' or 'Employer' roles. Alternatively, query the wp_usermeta table for meta_key='wp_capabilities' containing 'candidate' or 'employer'.Affected if Any users exist with Candidate or Employer roles
-
Inspect account status for Candidate/Employer usersCheck the user profile pages or user meta for account status fields (commonly 'is_active', 'account_status', or similar custom meta). Look for statuses marked as 'inactive', 'pending', or 'disabled'.Affected if Any Candidate or Employer accounts have status set to inactive, pending, or disabled but still exist in the system
-
Verify authentication behavior with inactive accountsAttempt to log in using a Candidate or Employer account known to have an inactive or pending status. Observe whether the login is successful or blocked.Affected if Login succeeds with an inactive or pending Candidate/Employer account when it should be denied
A site is affected if WP JobHunt plugin version 7.6 or lower is installed and there are Candidate or Employer users whose accounts are marked inactive or pending but who can still authenticate successfully.
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 the WP JobHunt plugin to a version beyond 7.6 once available, and audit user accounts to ensure only active accounts have login privileges.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7374 — 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-2025-7374 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