CVE-2025-39537

WP JobHunt <= 7.1 - Unauthenticated Insecure Direct Object Reference

2025-05-16 00:00
Bonds

Strategic Overview

Status
Unpatched
Affected Plugin
WP JobHunt
Affected Version
<= 7.1
CVSS
7.5High
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2025-39537
View all WP JobHunt vulnerabilities

At a glance

CVE-2025-39537 is a high-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP JobHunt WordPress plugin, affecting versions <= 7.1. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed May 2025, reported by Bonds.

Vulnerability Overview

The WP JobHunt plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 7.1 due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to perform an unauthorized action.

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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in WP JobHunt <= 7.1 takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. No fixed build of this plugin is recorded for WP JobHunt yet, so installs running <= 7.1 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?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-39537https://www.wordfence.com/threat-intel/vulnerabilities/id/cee0fbbb-64eb-4022-8220-dfcc5c37aa40https://nvd.nist.gov/vuln/detail/CVE-2025-39537

Related records

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