Security readout for executives and security teams
Plain-English summary
CVE-2026-3050 is a cross-site scripting issue in Horilla CRM’s Leads module. A user with limited privileges could place malicious content in the Notes field that runs in another user’s browser when viewed. Public sources say exploit material is available, but KEV does not list active exploitation.
Executive priority
Treat as a near-term remediation item for Horilla CRM environments. It is not rated critical, but public exploit availability raises urgency. Prioritize systems exposed to broad internal users, customer portals, or less-trusted authenticated accounts.
Technical view
The issue affects static/assets/js/global.js in horilla-opensource Horilla, where Notes handling in the Leads module permits cross-site scripting. CVSS 4.0 is 5.1 with network access, low complexity, low privileges required, and passive user interaction. Sources recommend upgrading to 1.0.3 and identify commit fc5c8e55988e89273012491b5f097b762b474546 as the patch.
Likely exposure
Organizations running Horilla CRM versions before 1.0.3 and using the Leads module are the primary exposure. The source bundle lists 1.0.3 under affected versions, but the description and release reference identify 1.0.3 as the recommended fixed version.
Exploitation context
Remote exploitation is reported possible, with low privileges required and user interaction needed. Exploit material has been published in a public repository. There is no provided evidence of known active exploitation, and CVE KEV status is false.
Researcher notes
Key uncertainty: source data conflicts by listing 1.0.3 as affected while also recommending 1.0.3 as fixed. Base validation on the release tag and patch commit, and confirm with vendor advisories. Avoid assuming active exploitation without additional evidence.
Mitigation direction
- Upgrade Horilla CRM to version 1.0.3 or later per vendor-linked release guidance.
- Review the referenced patch commit if maintaining a fork or custom deployment.
- Restrict untrusted access to CRM lead creation or editing until upgraded.
- Monitor vendor project guidance for any corrected affected-version details.
Validation and detection
- Inventory Horilla CRM deployments and identify installed versions.
- Confirm whether the Leads module is enabled and used.
- Verify version 1.0.3 or the referenced patch commit is present.
- Review recent Leads Notes entries for suspicious script-like content.
- Check application logs for unusual authenticated lead-editing activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-3050 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.1 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
5.1MediumVector: 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
Source materials
- CVE List V5 sourceCVE List V5
- VDB-347408 | horilla-opensource horilla Leads global.js cross site scriptingCVE reference · vdb-entry, technical-description
- VDB-347408 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference · signature, permissions-required
- Submit #757314 | Horilla CRM < 1.0.3 Cross Site ScriptingCVE reference · third-party-advisory
- https://github.com/Stolichnayer/Horilla-CRM-Stored-XSSCVE reference · exploit
- https://github.com/Horilla-opensource/Horilla-crm/commit/fc5c8e55988e89273012491b5f097b762b474546CVE reference · patch
- https://github.com/horilla-opensource/horilla-crm/releases/tag/1.0.3CVE reference · patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.