Skip to main content
Vulnerability Database/CVE-2026-63432

CVE-2026-63432: Horilla HR Software Information Disclosure

CVE-2026-63432 is an information disclosure vulnerability in Horilla HR and CRM software that exposes password hashes and sensitive user data through template attribute traversal. This article covers the technical details, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-63432 Overview

CVE-2026-63432 is an information disclosure vulnerability in Horilla, an open-source HR and CRM platform. The flaw affects the get_mail_preview handlers in recruitment/views/actions.py and employee/not_in_out_dashboard.py. These handlers render a user-controlled body with the full Django request object placed in the template context. An authenticated attacker holding a valid CSRF token can abuse Django template attribute traversal to read request.user.password, request.META, and related user attributes. The exposed data includes password hashes, personal information, and server request metadata. The issue affects Horilla from 1.0.0 up to 1.6.0 and 2.0.0, and is fixed in versions 1.6.0 and 2.0.0.

Critical Impact

Authenticated users can extract Django password hashes and sensitive request metadata through template attribute traversal, enabling offline password cracking and downstream account compromise.

Affected Products

  • Horilla HR versions 1.0.0 through 1.5.x
  • Horilla HR pre-release 2.0.0 development builds
  • recruitment and employee Django applications shipped with Horilla

Discovery Timeline

  • 2026-09-25 - CVE-2026-63432 published to NVD
  • 2026-09-28 - Last updated in NVD database

Technical Details for CVE-2026-63432

Vulnerability Analysis

The vulnerability is a server-side template injection pattern classified under [CWE-94] Improper Control of Generation of Code. Horilla's mail preview endpoints at /recruitment/get-mail-preview/ and /employee/get-employee-mail-preview render an administrator-supplied email body as a Django template. The rendering context exposes the entire HTTP request object, which transitively references the authenticated user, session, and server environment.

Django's template language intentionally restricts arbitrary code execution, so an attacker cannot invoke methods with arguments or call eval-style primitives. However, the language permits attribute and dictionary traversal through dotted notation. This allows traversal from request into request.user.password (the hashed password stored on the User model) and into request.META, which carries headers, environment variables, and potentially secrets injected by the deployment environment.

Exploitation requires only an authenticated session and a valid CSRF token. The demonstrated impact is sensitive information disclosure, with password hashes enabling offline cracking against Django's PBKDF2 or configured hasher. Successful recovery of a cleartext password leads to full account takeover of any user whose session triggered the preview call.

Root Cause

The mail preview handlers passed the raw Django request into Template.render(Context({...})) without sanitizing which attributes a template author could reach. Any user permitted to craft mail template bodies could insert expressions such as {{ request.user.password }} and observe the rendered output in the preview response.

Attack Vector

An authenticated user issues a POST request to the preview endpoint with a template body containing attribute-traversal expressions. The server renders the expressions against the live request context and returns the resolved values in the HTTP response body. Attackers do not need administrative privileges beyond access to the mail template preview feature.

python
# Patch excerpt - base/methods.py
 import random
 import re
 from datetime import date, datetime, time, timedelta
+from types import SimpleNamespace
 
 import pandas as pd
 import pdfkit

# Patch excerpt - employee/not_in_out_dashboard.py
 from base.backends import ConfiguredEmailBackend
 from base.forms import MailTemplateForm
-from base.methods import export_data, generate_pdf, sanitize_mail_template_body
+from base.methods import (
+    build_safe_template_request,
+    export_data,
+    generate_pdf,
+    sanitize_mail_template_body,
+    sanitize_mail_template_placeholders,
+)

Source: GitHub Commit bd3eed2 and GitHub Commit f1ca7cb. The fix introduces build_safe_template_request and sanitize_mail_template_placeholders, replacing the raw request with a SimpleNamespace that exposes only safe attributes.

Detection Methods for CVE-2026-63432

Indicators of Compromise

  • POST requests to /recruitment/get-mail-preview/ or /employee/get-employee-mail-preview with request bodies containing Django template expressions referencing request.user, request.META, or request.session.
  • Preview response payloads containing strings matching Django password hash prefixes such as pbkdf2_sha256$, argon2$, or bcrypt$.
  • Repeated preview requests from a single authenticated session enumerating different attribute paths.

Detection Strategies

  • Deploy a web application firewall rule that inspects POST bodies to the two preview endpoints and flags Django template delimiters {{ and }} combined with the token request..
  • Enable Django request logging and parse logs for get-mail-preview paths correlated with 200 responses larger than typical preview sizes.
  • Review the Horilla HorillaMailTemplate table for stored template bodies containing suspicious attribute traversal expressions.

Monitoring Recommendations

  • Alert on any authenticated user issuing more than a small threshold of preview requests per minute.
  • Monitor outbound responses from the preview endpoints for occurrences of hashed credential patterns.
  • Track changes to mail template records with audit logging to attribute abuse to a specific user account.

How to Mitigate CVE-2026-63432

Immediate Actions Required

  • Upgrade Horilla to version 1.6.0 or 2.0.0, which contain the build_safe_template_request sanitization helper.
  • Rotate Django SECRET_KEY and force a password reset for all accounts if preview endpoints were reachable by untrusted users prior to patching.
  • Restrict access to mail template preview URLs to a narrow set of administrator roles while patching is scheduled.

Patch Information

The fix is delivered in commits bd3eed2 and f1ca7cb and shipped in the Horilla 2.0.0 release. Full details are documented in the GitHub Security Advisory GHSA-9p83-4w63-7c24. The patch replaces the raw request object in the template context with a sanitized SimpleNamespace exposing only approved fields.

Workarounds

  • Block the /recruitment/get-mail-preview/ and /employee/get-employee-mail-preview routes at a reverse proxy until an upgrade is applied.
  • Apply a temporary middleware that strips Django template syntax ({{, }}, {%, %}) from request bodies destined for the preview endpoints.
  • Audit and remove any stored HorillaMailTemplate records whose bodies contain request. traversal expressions.
bash
# Nginx reverse proxy snippet to block preview endpoints pending patch
location ~ ^/(recruitment/get-mail-preview|employee/get-employee-mail-preview) {
    return 403;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.