LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24034: Horilla has File Upload XSS

Horilla is a free and open source Human Resource Management System (HRMS). In versions prior to 1.5.0, a cross-site scripting vulnerability can be triggered because the extension and content-type are not checked during the profile photo update step. Version 1.5.0 fixes the issue.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Horilla HRMS versions before 1.5.0 allow a logged-in user to upload a profile photo without proper file extension or content-type checks. This can cause cross-site scripting, potentially letting an attacker run script in a user’s browser. The impact is limited but relevant because HR systems handle sensitive employee data.

Executive priority

Prioritize remediation in normal patch cycles, faster for internet-facing Horilla instances or environments with many non-admin users. This is not currently evidenced as actively exploited, but HRMS data sensitivity makes timely upgrade prudent.

Technical view

CVE-2026-24034 is a file upload XSS issue in Horilla before 1.5.0. The profile photo update flow does not validate extension and content-type. CVSS 3.1 is 5.4: network-accessible, low complexity, low privileges required, no user interaction, with low confidentiality and integrity impact. The advisory maps it to CWE-434.

Likely exposure

Organizations running Horilla versions earlier than 1.5.0 are exposed, especially if regular user accounts can update profile photos. Internet exposure increases likelihood of account-driven abuse, but the source indicates low privileges are required.

Exploitation context

The provided sources do not report active exploitation, and this CVE is not marked KEV. Exploitation requires a valid low-privileged account. The vulnerability is in upload validation and results in XSS rather than server-side code execution, based on available sources.

Researcher notes

Evidence is limited to the CVE record, GitHub advisory, and 1.5.0 release reference. The sources name the vulnerable flow and fix version but do not provide detailed patch diffs, exploit observations, or compensating controls beyond upgrading.

Mitigation direction

  • Upgrade Horilla to version 1.5.0 or later.
  • Review vendor advisory and release notes for deployment-specific guidance.
  • Restrict profile photo upload access where operationally feasible until upgraded.
  • Monitor HRMS accounts for unusual profile updates or suspicious user activity.

Validation and detection

  • Inventory Horilla deployments and record running versions.
  • Confirm any version earlier than 1.5.0 is flagged as vulnerable.
  • Verify profile photo upload controls after upgrading.
  • Check logs for unusual profile photo update activity.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24034 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2026-24034Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
horilla-opensourcehorilla< 1.5.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.