# CVE-2025-48868: Horilla vulnerable to authenticated RCE via eval() in project_bulk_archive

> Authenticated attackers can execute arbitrary system commands via unsafe eval() usage in the project bulk archive feature.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2025
- **Updated:** 24 Sep 2025
- **Also known as:** GHSA-h6qj-pwmx-wjhw

## What is CVE-2025-48868?

CVE-2025-48868 is a high-severity code injection vulnerability in horilla-opensource horilla, published on 24 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Horilla is a free and open source Human Resource Management System (HRMS). An authenticated Remote Code Execution (RCE) vulnerability exists in Horilla 1.3.0 due to the unsafe use of Python’s eval() function on a user-controlled query parameter in the project_bulk_archive view. This allows privileged users (e.g., administrators) to execute arbitrary system commands on the server. While having Django’s DEBUG=True makes exploitation visibly easier by returning command output in the HTTP response, this is not required. The vulnerability can still be exploited in DEBUG=False mode by using blind payloads such as a reverse shell, leading to full remote code execution. This issue has been patched in version 1.3.1.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

## Which versions are affected by CVE-2025-48868?

It affects 1 product.


Products: Horilla Horilla.

## How do I fix CVE-2025-48868?

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

## Is CVE-2025-48868 being exploited?

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

Public exploit code:

- Horilla v1.3 - RCE (exploitdb)

## 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-2025-48868 and fix it if it is affected.

What it is: CVE-2025-48868 is a high-severity code injection vulnerability in horilla-opensource horilla, published on 24 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-48868 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-2025-48868/ (Markdown: https://insights.sbomify.com/CVE-2025-48868/index.md)
```

## Sources

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

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