Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged user
-
DeliverySend crafted 'columns' POST to export_data
-
ExploitInject Python via literal_eval-valid payload
-
Executionexec() defines malicious function
-
ImpactExecute OS commands as root in container
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a valid authenticated Horilla account with permission to reach HorillaListView.export_data (list/export functionality); the attacker submits a crafted 'columns' POST parameter whose field_tuple[1] value remains valid under ast.literal_eval while injecting Python into a default argument evaluated at function definition. No non-default configuration is needed and no user interaction is required. Exploitation is limited only by the need for authentication (PR:L); impact is amplified in the shipped horilla/horilla-hr Docker image, which runs the process as root, so commands execute with root privileges. Affects all versions prior to 2.0.0. |
| Impact | This is a genuine high-priority vulnerability. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) describes network-reachable, low-complexity code injection requiring only a low-privileged authenticated account and no user interaction, yielding full confidentiality, integrity, and availability impact via arbitrary OS command execution (CWE-94). The vector is internally consistent with the description: an authenticated user submits a crafted 'columns' POST parameter that is interpolated into Python source and passed to exec(). Exploitation status is 'no public exploit identified at time of analysis' for weaponized code - KEV is not listed and no EPSS score was provided in the input, so widespread automated exploitation cannot be asserted; however a VulDB advisory entry exists (vuldb.com/vuln/410491) alongside the GitHub Security Advisory (GHSA-5g4v-4rv4-r26f). The one factor that meaningfully raises real-world impact is deployment context: the shipped Docker image runs the application as root, so successful RCE grants root on the container. The main dampener is the PR:L requirement - an attacker needs a valid application account - which makes this most dangerous for multi-tenant or employee-facing HR deployments where low-privilege accounts are common. No signals conflict; the primary missing data are EPSS probability and a confirmed public POC. |
| Exploit ScenarioDerived | A low-privileged but authenticated Horilla user (e.g., a regular employee account) invokes a list export and submits a crafted 'columns' POST parameter whose field value stays valid under ast.literal_eval while injecting Python syntax into a default argument evaluated when the dynamically generated function is defined via exec(). This executes attacker-chosen OS commands with the application process's privileges - root inside the shipped Docker image. No public weaponized exploit is identified at time of analysis, though a VulDB advisory and GitHub Security Advisory document the flaw. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 25, 2026
Authenticated code injection in Horilla HR (horilla-hr) before 2.0.0 lets any user with access to the HorillaListView export functionality run arbitrary operating-system commands with the privileges of the application process - root, in the project's shipped horilla/horilla-hr Docker image. The issue is rated CVSS v3.1 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H): exploitable remotely over the network with low privileges, requiring only a valid account able to reach the list/export endpoint, with no user interaction and no non-default configuration. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor released a fix in version 2.0.0.
RemediationAI
Upgrade to Horilla HR 2.0.0 or later; the vendor fix is confirmed in that release (patch status: Vendor-released patch: 2.0.0) - see the advisory at https://github.com/horilla/horilla-hr/security/advisories/GHSA-5g4v-4rv4-r26f and the release at https://github.com/horilla/horilla-hr/releases/tag/2.0.0, and for container deployments migrate from the deprecated horilla/horilla image to horilla/horilla-hr:2.0.0 (or newer). If immediate upgrade is not possible, the highest-value compensating control is least privilege on the process itself: because the shipped image runs as root, reconfiguring the container or service to run as a non-root user with a read-only application filesystem caps injected commands at the container user's rights (side effect: some uploads, media writes and report generation paths may need explicit writable volumes). Second, restrict who can reach the list/export functionality by removing the export permission from non-administrative roles and, where a reverse proxy is available, blocking or IP-allowlisting the export endpoints used by HorillaListView (side effect: legitimate bulk exports unavailable to those users). Third, treat the application host and container as compromised if an unpatched instance has been internet-exposed, since the injected code executes with the app process's privileges and can read database credentials and environment secrets; rotate those credentials. Avoid relying on WAF signatures for this bug, as the payload lives inside an otherwise well-formed 'columns' parameter. Note the 2.0.0 release also repins Django to ~=5.2.17 to address CVE-2025-64459 and fixes a request thread-local leak that mis-attributed created_by/modified_by, so upgrading resolves additional issues beyond this CVE.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Root cause is CWE-94 (Improper Control of Generation of Code / code injection) in a Python/Django application. HorillaListView.export_data in horilla_views/generic/cbv/views.py takes the authenticated user's 'columns' POST parameter, extracts field_tuple[1], and interpolates that value directly into a string (dynamic_fn_str) that is turned into a Python function definition and handed to exec(). Because the attacker-controlled value is placed into a position that remains syntactically valid after ast.literal_eval - specifically a default argument, which Python evaluates at function-definition time rather than at call time - the validation step does not neutralize the injected syntax, and arbitrary Python code is compiled and executed when the generated function is defined. This is a classic 'string-built-source plus exec()' pattern compounded by a flawed sanitizer that only enforces literal-evaluability; the correct approach is never to build source text from user input. The Django framework underneath is not the vulnerable component (the release notes indicate Django was separately re-pinned from Django==5.2 to Django~=5.2.17 for CVE-2025-64459), so the exposure is entirely within Horilla's own view layer. Impact is amplified in the official horilla/horilla-hr image, which runs the application as root, converting an application-level RCE into command execution as root inside the container.
Know when Python gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Network-reachable export endpoint, low-complexity injection needing only a low-privileged account (PR:L) and no interaction; RCE as root yields full C/I/A impact, scope unchanged within the process.
Primary rating from Vendor (github).
CVSS VectorVendor: github
Lifecycle Timeline
2DescriptionCVE.org
Horilla is an HR and CRM software. Prior to 2.0.0, HorillaListView.export_data in horilla_views/generic/cbv/views.py accepts an authenticated user's columns POST parameter, takes field_tuple[1], interpolates it into dynamic_fn_str as Python source, and passes the generated function definition to exec(). A crafted string that remains valid under ast.literal_eval can inject Python syntax into a default argument evaluated during function definition, allowing arbitrary operating-system commands to execute with the application process privileges, including root privileges in the shipped Docker image. This issue is fixed in version 2.0.0.
Articles & Coverage 1
Technical POC Analysis
CWE-94 (Improper Control of Generation of Code).
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
Horilla HR deployments running versions before 2.0.0 are exposed to an authenticated code injection flaw that can let a low-privileged user execute operating-system commands with the privileges of the application process-root in the vendor's shipped Docker image. This matters to leadership because a compromised HR platform can expose sensitive employee records, disrupt payroll and HR operations, and provide a foothold for broader network compromise, although no public exploit identified at time of analysis and a vendor patch is available in version 2.0.0. Affected organizations should prioritize patching network-accessible instances and review access to the export functionality.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Wazuh SIEM platform versions 4.4.0 through 4.9.0 contain an unsafe deserialization vulnerability in the DistributedAPI t
BentoML version 1.4.2 and earlier contains an unauthenticated remote code execution vulnerability through insecure deser
pgAdmin 4 contains critical remote code execution vulnerabilities in the Query Tool download and Cloud Deployment endpoi
The renderLocalView function in render/views.py in graphite-web in Graphite 0.9.5 through 0.9.10 uses the pickle Python
BentoML is a Python library for building online serving systems optimized for AI apps and model inference. Rated critica
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
pyLoad download manager version prior to 0.5.0b3.dev77 exposes the Flask SECRET_KEY through an unauthenticated endpoint.
Langflow (a visual LLM pipeline builder) contains a critical unauthenticated code execution vulnerability (CVE-2026-3301
In Mercurial before 4.1.3, "hg serve --stdio" allows remote authenticated users to launch the Python debugger, and conse
Unauthenticated remote code execution affects Kestra OSS (the open-source event-driven orchestration platform) prior to
Unauthenticated remote code execution in Marimo ≤0.20.4 allows attackers to execute arbitrary system commands via the `/
pyLoad is the free and open-source Download Manager written in pure Python. Rated medium severity (CVSS 5.3), this vulne
EUVD-2026-87370
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB