CVE-2024-11917 HIGH

CVE-2024-11917: JobSearch WP Job Board <= 2.9.2 - Authentication Bypass via Social Logins

Vendor Eyecix
Product JobSearch WP Job Board
Weakness CWE-287 · Improper authentication
Published April 25, 2025
Last update April 8, 2026

CVSS base score

8.1/10
Attack vector Network
Attack complexity High
Privileges required None
User interaction None
Confidentiality High
Integrity High

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

What the vulnerability does

01Description

The JobSearch WP Job Board plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 2.9.2. This is due to improper configurations in the 'jobsearch_xing_response_data_callback', 'set_access_tokes', and 'google_callback' functions. This makes it possible for unauthenticated attackers to log in as the first connected Xing user, or any connected Xing user if the Xing id is known. It is also possible for unauthenticated attackers to log in as the first connected Google user if the user has logged in, without subsequently logging out, in thirty days. The vulnerability was partially patched in version 2.8.4.

Explanation of Vulnerability in Simple Terms

02Summary

JobSearch WP Job Board versions up to 2.9.2 contain an authentication bypass vulnerability. An attacker can gain unauthorized access to the plugin without valid credentials due to improper authentication checks. This allows full control over job board functionality and potentially sensitive user data. Update immediately to a version newer than 2.9.2.

What an attacker can do

03Attacker Capabilities

Bypass authentication and gain unauthorized access to the job board without valid credentials.

Potential impact on your site

04Site Impact

Attackers can access and modify job listings, user accounts, and sensitive job board data without permission.

Conditions required to exploit

05Prerequisites

Network access to the WordPress site; no authentication or user interaction required.

Key dates

06Disclosure timeline

April 25, 2025 CVE published
April 8, 2026 Record updated