WP JobHunt Plugin up to 7.1 on WordPress authentication by alternate name
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in WP JobHunt Plugin up to 7.1 on WordPress. It has been classified as problematic. Impacted is an unknown function. This manipulation causes authentication by alternate name. The identification of this vulnerability is CVE-2024-11283. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in WP JobHunt Plugin up to 7.1 on WordPress. It has been declared as problematic. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a authentication by alternate name vulnerability. The CWE definition for the vulnerability is CWE-289. The product performs authentication based on the name of a resource being accessed, or the name of the actor performing the access, but it does not properly check all possible names for that resource or actor. As an impact it is known to affect confidentiality. The summary by CVE is:
The WP JobHunt plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 7.1. This is due to wp_ajax_google_api_login_callback function not properly verifying a user's identity prior to authenticating them. This makes it possible for unauthenticated attackers to access arbitrary candidate accounts.
The weakness was shared by Tonn. The advisory is shared at wordfence.com. This vulnerability is known as CVE-2024-11283 since 11/15/2024. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (Wordfence): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Authentication by alternate nameCWE: CWE-289 / CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/15/2024 🔍03/14/2025 🔍
03/14/2025 🔍
07/08/2025 🔍
Sources
Advisory: wordfence.comResearcher: Tonn
Status: Not defined
CVE: CVE-2024-11283 (🔍)
GCVE (CVE): GCVE-0-2024-11283
GCVE (VulDB): GCVE-100-299689
Entry
Created: 03/14/2025 09:11Updated: 07/08/2025 17:40
Changes: 03/14/2025 09:11 (62), 07/08/2025 17:40 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.