# CVE-2026-24010: Horilla has HTML Injection Issue that, with Phishing, Leads to Account Takeover

> Authenticated users can upload malicious HTML files to create phishing pages, stealing credentials and enabling account takeover.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2026
- **Updated:** 22 Jan 2026
- **Also known as:** GHSA-5jfv-gw8w-49h3

## What is CVE-2026-24010?

CVE-2026-24010 is a high-severity vulnerability in horilla-opensource horilla, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Horilla is a free and open source Human Resource Management System (HRMS). A critical File Upload vulnerability in versions prior to 1.5.0, with Social Engineering, allows authenticated users to deploy phishing attacks. By uploading a malicious HTML file disguised as a profile picture, an attacker can create a convincing login page replica that steals user credentials. When a victim visits the uploaded file URL, they see an authentic-looking "Session Expired" message prompting them to re-authenticate. All entered credentials are captured and sent to the attacker's server, enabling Account Takeover. Version 1.5.0 patches the issue.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-474 (Use of Function with Inconsistent Implementations)

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

It affects 1 product.


Products: Horilla Horilla.

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

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

## Is CVE-2026-24010 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24010 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-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)
- [CVE-2025-48869](https://insights.sbomify.com/CVE-2025-48869/): Horilla Unauthorized Access to Candidate Resume Files Due to Broken Access Control (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-24010 is a high-severity vulnerability in horilla-opensource horilla, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24010 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-24010/ (Markdown: https://insights.sbomify.com/CVE-2026-24010/index.md)
```

## Sources

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

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