CVE-2026-9237 MEDIUM

CVE-2026-9237: Employee, Leave and Recruitment Management System <= 1.2.2 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Job Deletion via crewhrm_singleJobAction AJAX Action

Vendor Crewhrm
Product Employee, Leave and Recruitment Management System – Crew HRM
Weakness CWE-862 · Missing authorization
Published July 9, 2026
Last update July 9, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality None
Integrity Low

CVSS vector

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

What the vulnerability does

01Description

The Employee, Leave and Recruitment Management System – Crew HRM plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 1.2.2. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete, archive, unarchive, and duplicate arbitrary job listings — along with their associated stages, meta, addresses, and applications — by supplying an arbitrary integer job_id. The nonce verified by Dispatcher::dispatch() is exposed to all authenticated front-end visitors via wp_head script localization, meaning subscribers can trivially obtain it and satisfy the nonce check without possessing any elevated privilege.

Explanation of Vulnerability in Simple Terms

02Summary

Crew HRM versions up to 1.2.2 lack proper authorization checks, allowing authenticated users to modify data they should not have access to. An attacker with a low-privilege account can change records without the system verifying their permissions. This affects the integrity of employee, leave, and recruitment data. Update to a version newer than 1.2.2.

What an attacker can do

03Attacker Capabilities

Modify employee, leave, or recruitment records without proper authorization.

Potential impact on your site

04Site Impact

Unauthorized changes to HR data by internal users with limited permissions; data integrity compromised.

Conditions required to exploit

05Prerequisites

Attacker must have a valid low-privilege user account on the system.

Key dates

06Disclosure timeline

July 9, 2026 CVE published
July 9, 2026 Record updated

Related vulnerabilities

08Related CVE