Horilla up to 1.x Attendance Approval approve-validate-attendance-request approve_validate_attendance_request cross-site request forgery

Summaryinfo

A vulnerability described as problematic has been identified in Horilla up to 1.x. Impacted is the function approve_validate_attendance_request of the file /attendance/approve-validate-attendance-request of the component Attendance Approval. Such manipulation leads to cross-site request forgery. This vulnerability is uniquely identified as CVE-2026-86066. The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Horilla up to 1.x. Affected by this issue is the function approve_validate_attendance_request of the file /attendance/approve-validate-attendance-request of the component Attendance Approval. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. Impacted is integrity. CVE summarizes:

Horilla is an HR and CRM software. Prior to 2.0.0, approve_validate_attendance_request at /attendance/approve-validate-attendance-request/ changes attendance_validated, is_validate_request_approved, approved_by, and related pending-request state through an HTTP GET before calling attendance.save(), so Django does not require CSRF validation for the action. An unauthenticated attacker can cause a logged-in manager with attendance.change_attendance to make a top-level request that carries the manager's SameSite=Lax session cookie, silently approving attendance with the victim's privileges and attributing the approval to the victim in the audit trail. This issue is fixed in version 2.0.0.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-86066 since 09/04/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.

Upgrading to version 2.0.0 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-87371). Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Horilla

Version

• 1.x

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion