Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-48868 is a high-severity Eval Injection (CWE-95) vulnerability in Horilla Horilla. Its CVSS base score is 7.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique JavaScript (T1059.007); ranked in the top 18% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Horilla, an open source Human Resource Management System, contains an authenticated remote code execution vulnerability in version 1.3.0. The flaw stems from unsafe use of Python’s eval() function on a user-controlled query parameter within the project_bulk_archive view, allowing arbitrary command execution on the server. The issue is tracked as CWE-95 and carries a CVSS 3.1 score of 7.2.
Privileged authenticated users such as administrators can exploit the vulnerability to run system commands. Exploitation is simplified when Django DEBUG mode is enabled because command output appears in responses, but blind techniques such as reverse shells succeed even when DEBUG is false, resulting in full remote code execution and complete server compromise.
The project has released version 1.3.1 to address the issue, with the fix documented in the corresponding GitHub commit and security advisory. The EPSS score remains flat at 0.0563 with no material increase observed after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-30970
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.2
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and code analysis can discover eval-injection flaws but does not stop their introduction.
Input validation explicitly requires neutralizing untrusted data before it reaches dynamic evaluation constructs such as eval.
Secure-development standards and tools can mandate safe coding patterns that avoid unsafe dynamic evaluation.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input neutralization and avoidance of unsafe dynamic evaluation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect eval injection vulnerabilities before deployment.
Secure development life cycle mandates input validation and safe coding practices that directly prevent eval injection.
Application security requirements include rules against dynamic code execution of untrusted input.
Secure architecture principles discourage unsafe dynamic evaluation constructs.
Secure coding explicitly requires neutralization of input before dynamic evaluation, directly mitigating eval injection.
Separation of environments limits the blast radius if eval injection occurs in non-production.