Skip to main content
VulnerabilityPublished Updated

CVE-2026-63432: horilla-hr · Code Injection

Affects horilla-hrSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.0.0 or 1.6.0 when convenient.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.0, 1.6.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade horilla-hr to 2.0.0 or 1.6.0; horilla/horilla-hr to 2.0.0.

Affected software

ProductAffectedFixed in
horillahorilla-hrAffected
  • >=2.0.0-beta.1 <2.0.0
Fixed in
  • 2.0.0
horillahorilla-hrAffected
  • >=1.0.0 <1.6.0
Fixed in
  • 1.6.0
GitHubhorilla/horilla-hrpkg:github/horilla/horilla-hrOther threatsAffected
  • >=2.0.0-beta.1 <2.0.0
Fixed in
  • 2.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in horilla-hr versions 1.6.0 and 2.0.0. Users should upgrade to these or later versions to remediate the issue. No other mitigation steps are indicated by the vendor advisory.

Description

Horilla is an HR and CRM software. From 1.0.0 until 1.6.0 and 2.0.0, the get_mail_preview handlers in recruitment/views/actions.py and employee/not_in_out_dashboard.py render a user-controlled body at /recruitment/get-mail-preview/ and /employee/get-employee-mail-preview with the full request object in the Django template context. An authenticated user with a valid CSRF token can use template attribute traversal to read request.user.password, request.META, and related-user attributes, exposing password hashes, personal data, and server request metadata. Django template restrictions prevent arbitrary code execution through this primitive, so the demonstrated impact is information disclosure and possible offline password cracking or account compromise. This issue is fixed in versions 1.6.0 and 2.0.0.

References

Community reviews

Loading reviews…