Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2025-48868: Authenticated RCE in Horilla project_bulk_archive

Published Sep 24, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.2High · v3.1
EPSS2.5%85th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Horilla
IdentifiersCVE-2025-48868CWE-95 · Improper Neutralization of…

CVE-2025-48868 is an authenticated remote code execution vulnerability in Horilla HRMS version 1.3.0. The flaw is caused by unsafe use of Python's eval() on a user-controlled query parameter in the project_bulk_archive view. Because attacker-supplied input is evaluated as Python code, a privileged authenticated user, such as an administrator, can execute arbitrary commands on the underlying server. The issue is easier to observe when Django is running with DEBUG=True because command output may be returned in the HTTP response, but DEBUG mode is not required for exploitation. In production-style DEBUG=False deployments, the vulnerability remains exploitable through blind payloads, including reverse-shell style command execution.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in full remote code execution on the Horilla server in the security context of the application process. An attacker can execute arbitrary system commands, deploy malware or web shells, access or modify HRMS data, steal credentials or secrets available to the application, pivot further into the environment, and potentially disrupt service integrity and availability. Because exploitation is possible even with DEBUG disabled, the risk is not limited to development deployments.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict access to Horilla administrative and other privileged interfaces to only trusted users and tightly controlled networks, reduce the number of accounts with sufficient privileges to reach the vulnerable functionality, and monitor for suspicious requests targeting the project_bulk_archive view or containing expression-like payloads. Ensure Django DEBUG is disabled in production to avoid returning command output directly in responses, although this does not eliminate the vulnerability. Additional compensating controls may include WAF rules or reverse-proxy filtering for malicious query parameter patterns, application allowlisting, and outbound network egress controls to hinder reverse-shell style exploitation.

Remediation

Patch, then assume compromise.

Upgrade Horilla to version 1.3.1 or later, where the issue is patched. Remove the unsafe eval() usage from the project_bulk_archive view and replace it with strict input validation and safe parsing mechanisms appropriate to the expected parameter format. Review the codebase for any additional dynamic evaluation patterns such as eval/exec or equivalent unsafe deserialization or expression handling. After patching, rotate any credentials or secrets that may have been exposed to the application and investigate for signs of compromise if vulnerable versions were exposed to privileged users.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
HorillaHorillaapplication
FAQ

Frequently asked questions

Is CVE-2025-48868 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-48868 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-48868?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2025-48868.
Is there a patch for CVE-2025-48868?
Upgrade Horilla to version 1.3.1 or later, where the issue is patched. Remove the unsafe eval() usage from the project_bulk_archive view and replace it with strict input validation and safe parsing mechanisms appropriate to the expected parameter format.
What products are affected by CVE-2025-48868?
Horilla.
How severe is CVE-2025-48868?
CVE-2025-48868 has a CVSS v3.1 score of 7.2 (High) and an EPSS score of 2.5% (85th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

6 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.