{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24037 exists.","fix":"No fix has been published for CVE-2026-24037 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-24037 is a medium-severity cross-site scripting vulnerability in horilla-opensource horilla, published on 22 Jan 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-24037 and fix it if it is affected.\n\nWhat it is: CVE-2026-24037 is a medium-severity cross-site scripting vulnerability in horilla-opensource horilla, published on 22 Jan 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24037 exists.\n\nAffected product: horilla-opensource horilla. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-24037/ (Markdown: https://insights.sbomify.com/CVE-2026-24037/index.md)","id":"CVE-2026-24037","markdown":"https://insights.sbomify.com/CVE-2026-24037/index.md","name":"CVE-2026-24037","record":{"aliases":["GHSA-rqw5-fjm4-rgvm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Horilla HRM","requires_auth":"high_privilege","summary":"Attackers can bypass XSS filters to execute scripts, redirect users, and steal CSRF tokens in the Horilla HRM system.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"horilla","vendor":"horilla"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Horilla is a free and open source Human Resource Management System (HRMS). In version 1.4.0, the has_xss() function attempts to block XSS by matching input against a set of regex patterns. However, the regexes are incomplete and context-agnostic, making them easy to bypass. Attackers are able to redirect users to malicious domains, run external JavaScript, and steal CSRF tokens that can be used to craft CSRF attacks against admins. This issue has been fixed in version 1.5.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Horilla HRM has XSS Bypass through Project Name","id":"CVE-2026-24037","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Horilla HR has 2FA Bypass through its OTP Handling Logic","id":"CVE-2026-24038"},"packages":[],"prev":{"headline":"Horilla Exposes Unpublished Job Disclosures through Unauthenticated API","id":"CVE-2026-24036"},"products":["horilla"],"published":"2026-01-22","related":[{"cvss_score":9.9,"headline":"Horrila Stored XSS Vulnerability via Ticket Comment section","id":"CVE-2025-59832","kev_date_added":null,"published":"2025-09-25"},{"cvss_score":8.8,"headline":"Horilla has HTML Injection Issue that, with Phishing, Leads to Account Takeover","id":"CVE-2026-24010","kev_date_added":null,"published":"2026-01-22"},{"cvss_score":8.1,"headline":"Horilla HR has 2FA Bypass through its OTP Handling Logic","id":"CVE-2026-24038","kev_date_added":null,"published":"2026-01-22"},{"cvss_score":7.7,"headline":"Horilla Stored XSS Vulnerability via File Upload in Reimbursement Panel","id":"CVE-2025-59524","kev_date_added":null,"published":"2025-09-24"},{"cvss_score":7.7,"headline":"Horilla has Improper Input Sanitization Leading to XSS and Admin Account Takeover","id":"CVE-2025-59525","kev_date_added":null,"published":"2025-09-24"},{"cvss_score":7.5,"headline":"Horilla Unauthorized Access to Candidate Resume Files Due to Broken Access Control","id":"CVE-2025-48869","kev_date_added":null,"published":"2025-09-24"},{"cvss_score":7.2,"headline":"Horilla vulnerable to authenticated RCE via eval() in project_bulk_archive","id":"CVE-2025-48868","kev_date_added":null,"published":"2025-09-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-22","vendors":["horilla-opensource"]},"summary":"Attackers can bypass XSS filters to execute scripts, redirect users, and steal CSRF tokens in the Horilla HRM system.","url":"https://insights.sbomify.com/CVE-2026-24037/"}