CVE-2025-6585

WP JobHunt <= 7.2 - Authenticated (Subscriber+) Insecure Direct Object Reference to Arbitrary Account Deletion

2025-07-21 15:58
meghnine islem

Strategic Overview

Status
Unpatched
Affected Plugin
WP JobHunt
Affected Version
<= 7.2
CVSS
8.1High
Weakness type
CWE-20 · Improper Input Validation
CVE
CVE-2025-6585
View all WP JobHunt vulnerabilities

At a glance

CVE-2025-6585 is a high-severity Improper Input Validation vulnerability in the WP JobHunt WordPress plugin, affecting versions <= 7.2. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed July 2025, reported by meghnine islem.

Vulnerability Overview

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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on integrity, availability.

CWE-20: Improper Input Validation

WP JobHunt <= 7.2 carries this weakness at cs_remove_profile_callback(), and reaching it takes an account at Subscriber level or above. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.

The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. No fixed build of this plugin is recorded for WP JobHunt yet, so installs running <= 7.2 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C