dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-6585

HIGH · 8.1 CVSS v3.1 Published 2025-07-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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 Insecure Direct Object Reference in all versions up to, and including, 7.2 via the cs_remove_profile_callback() function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete accounts of other users including admins.

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 contains an IDOR vulnerability in the cs_remove_profile_callback() function. The function fails to validate that the requesting user has permission to delete the target user account, allowing any authenticated user with Subscriber-level access to delete arbitrary user accounts including administrators by manipulating a user-controlled key parameter.

MitigationUpdate the WP JobHunt plugin to a version beyond 7.2 which contains proper authorization validation. As an interim measure, restrict or monitor user registration and remove subscriber-level access from untrusted users until the patch can be applied.

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Locate the WP JobHunt plugin installation
    Check the WordPress plugins directory at /wp-content/plugins/ for a folder named 'wp-jobhunt' or similar, and verify the plugin files exist
    Affected if The WP JobHunt plugin folder is present in the plugins directory
  2. Determine the installed plugin version
    Access WordPress admin dashboard under Plugins > Installed Plugins and locate WP JobHunt, then read the version number displayed; alternatively, check the main plugin PHP file for a 'Version' header comment
    Affected if The installed version is 7.2 or lower, or the version cannot be determined (older unpatched releases)
  3. Verify the vulnerable function exists
    Search the plugin files for the function cs_remove_profile_callback() - typically found in includes or shortcodes directories, often in files related to user profiles
    Affected if The function cs_remove_profile_callback() is present in the plugin code
  4. Check for subscriber-level user accounts
    In WordPress admin, navigate to Users > All Users and review the 'Role' column for accounts with 'Subscriber' role, or query the wp_usermeta table where meta_key = 'wp_capabilities' and meta_value contains 'subscriber'
    Affected if There is at least one user account with Subscriber-level access (any subscriber can exploit this vulnerability)
  5. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify WP JobHunt shows as 'Active'
    Affected if The plugin is currently active and the above conditions are met

A user is affected if the WP JobHunt plugin is installed and active at version 7.2 or lower, and any Subscriber-level user account exists in the WordPress environment.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WP JobHunt plugin to a version beyond 7.2 which contains proper authorization validation. As an interim measure, restrict or monitor user registration and remove subscriber-level access from untrusted users until the patch can be applied.

Recommended fix Moderate confidence

Version 7.3 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the WP JobHunt plugin
  4. Click 'Update Now' to install the latest available version

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

Have this fixed 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 help mitigating

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-2025-6585 — 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-2025-6585 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