# CVE-2026-24037: Horilla HRM has XSS Bypass through Project Name

> Attackers can bypass XSS filters to execute scripts, redirect users, and steal CSRF tokens in the Horilla HRM system.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Jan 2026
- **Updated:** 22 Jan 2026
- **Also known as:** GHSA-rqw5-fjm4-rgvm

## What is CVE-2026-24037?

CVE-2026-24037 is a medium-severity cross-site scripting vulnerability in horilla-opensource horilla, published on 22 Jan 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Horilla is a free and open source Human Resource Management System (HRMS). In version 1.4.0, the has_xss() function attempts to block XSS by matching input against a set of regex patterns. However, the regexes are incomplete and context-agnostic, making them easy to bypass. Attackers are able to redirect users to malicious domains, run external JavaScript, and steal CSRF tokens that can be used to craft CSRF attacks against admins. This issue has been fixed in version 1.5.0.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-24037?

It affects 1 product.


Products: Horilla Horilla.

## How do I fix CVE-2026-24037?

No fix has been published for CVE-2026-24037 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-24037 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24037 exists.

## Other vulnerabilities in horilla-opensource horilla

- [CVE-2025-59832](https://insights.sbomify.com/CVE-2025-59832/): Horrila Stored XSS Vulnerability via Ticket Comment section (critical 9.9)
- [CVE-2026-24010](https://insights.sbomify.com/CVE-2026-24010/): Horilla has HTML Injection Issue that, with Phishing, Leads to Account Takeover (high 8.8)
- [CVE-2026-24038](https://insights.sbomify.com/CVE-2026-24038/): Horilla HR has 2FA Bypass through its OTP Handling Logic (high 8.1)
- [CVE-2025-59524](https://insights.sbomify.com/CVE-2025-59524/): Horilla Stored XSS Vulnerability via File Upload in Reimbursement Panel (high 7.7)
- [CVE-2025-59525](https://insights.sbomify.com/CVE-2025-59525/): Horilla has Improper Input Sanitization Leading to XSS and Admin Account Takeover (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24037 and fix it if it is affected.

What it is: CVE-2026-24037 is a medium-severity cross-site scripting vulnerability in horilla-opensource horilla, published on 22 Jan 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24037 exists.

Affected product: horilla-opensource horilla. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24037/ (Markdown: https://insights.sbomify.com/CVE-2026-24037/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24037
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24037
- OSV: https://osv.dev/vulnerability/CVE-2026-24037

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24037/
Summaries are generated and may contain mistakes; the official description above is the record.