VulnerabilityPublished 24 Feb 2026Updated 26 Feb 2026

CVE-2026-3050: horilla · Cross-site Scripting

Affects horillaSource CVE Database V5

Compare

Public exploit available · CVSS 5.1 Medium · fixed in 1.0.3 : patch horilla as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.0.3

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
horilla-opensourcehorilla	Affected =1.0.0 =1.0.1 =1.0.2	Fixed in–
GitHubhorilla-opensource/horilla-crm`pkg:github/horilla-opensource/horilla-crm`Other threats	Affected =1.0.0 =1.0.1 =1.0.2	Fixed in–

CPE configurations (1)

cpe:2.3:a:horilla:horilla:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-3050, organizations should immediately upgrade horilla to version 1.0.3 or later, which contains the official patch addressing the XSS vulnerability. Beyond patching, developers should implement robust input validation and output encoding on all user-supplied data, especially within the Leads Module and any components handling Notes or similar inputs. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of potential XSS attacks. Regularly audit and sanitize JavaScript code to prevent injection points. Security teams should monitor web application logs for suspicious input patterns indicative of XSS attempts. User education on recognizing phishing and suspicious links can reduce the risk of successful exploitation requiring user interaction. Additionally, consider deploying web application firewalls (WAFs) configured to detect and block common XSS payloads targeting horilla applications. Finally, integrate automated security testing into the development lifecycle to catch similar vulnerabilities early.

Description

A flaw has been found in horilla-opensource horilla up to 1.0.2. Impacted is an unknown function of the file static/assets/js/global.js of the component Leads Module. This manipulation of the argument Notes causes cross site scripting. The attack is possible to be carried out remotely. The exploit has been published and may be used. Upgrading to version 1.0.3 is recommended to address this issue. Patch name: fc5c8e55988e89273012491b5f097b762b474546. It is suggested to upgrade the affected component.

Impact

The primary impact of CVE-2026-3050 is the potential compromise of user sessions and data confidentiality through the execution of arbitrary scripts in the context of affected web applications. Attackers can exploit this vulnerability to steal cookies, perform actions on behalf of users, or deliver malicious payloads such as ransomware or phishing content. Although the vulnerability does not directly affect system availability or integrity, the resulting compromise of user trust and data privacy can lead to reputational damage and regulatory penalties. Organizations relying on horilla for lead management or customer interaction may face targeted attacks aiming to extract sensitive business information or disrupt operations. The remote exploitability and published proof-of-concept increase the risk of widespread exploitation, especially if patches are not applied promptly. The requirement for user interaction somewhat limits automated exploitation but does not eliminate risk, particularly in environments with high user engagement or where social engineering can be leveraged.

Summary

CVE-2026-3050 is a cross-site scripting (XSS) vulnerability identified in the horilla-opensource horilla product, specifically affecting versions 1.0.0 through 1.0.2. The vulnerability resides in the Leads Module, within the JavaScript file static/assets/js/global.js, where the Notes argument is improperly sanitized or validated. This flaw allows an attacker to inject malicious JavaScript code remotely by manipulating the Notes input parameter. The vulnerability does not require authentication but does require user interaction to trigger the malicious script execution, such as a victim clicking a crafted link or viewing a manipulated page. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:L), user interaction required (UI:P), and limited impact on confidentiality and integrity (VC:N, VI:L), with no impact on availability. The vendor has released version 1.0.3 to address this issue, with a patch identified by commit fc5c8e55988e89273012491b5f097b762b474546. While no known exploits are currently active in the wild, published exploit code increases the likelihood of exploitation attempts. The vulnerability is typical of reflected or stored XSS, enabling attackers to execute arbitrary scripts in the context of the victim's browser, potentially leading to session hijacking, credential theft, or defacement.

References

Community reviews

Loading reviews…