{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-24038 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-24038 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-24038 is a high-severity authentication bypass vulnerability in horilla-opensource horilla, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-24038 and fix it if it is affected.\n\nWhat it is: CVE-2026-24038 is a high-severity authentication bypass vulnerability in horilla-opensource horilla, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-24038 in the wild and no public exploit code.\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-24038/ (Markdown: https://insights.sbomify.com/CVE-2026-24038/index.md)","id":"CVE-2026-24038","markdown":"https://insights.sbomify.com/CVE-2026-24038/index.md","name":"CVE-2026-24038","record":{"aliases":["GHSA-hqpv-ff5v-3hwf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Horilla HRMS","requires_auth":"low_privilege","summary":"Attackers can bypass two-factor authentication in Horilla HRMS by omitting the OTP field, potentially compromising administrative accounts and sensitive HR data.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"horilla","vendor":"horilla"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Horilla is a free and open source Human Resource Management System (HRMS). In version 1.4.0, the OTP handling logic has a flawed equality check that can be bypassed. When an OTP expires, the server returns None, and if an attacker omits the otp field from their POST request, the user-supplied OTP is also None, causing the comparison user_otp == otp to pass. This allows an attacker to bypass two-factor authentication entirely without ever providing a valid OTP. If administrative accounts are targeted, it could lead to compromise of sensitive HR data, manipulation of employee records, and further system-wide abuse. 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":"none_known"},"has_fix":false,"headline":"Horilla HR has 2FA Bypass through its OTP Handling Logic","id":"CVE-2026-24038","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Horilla's Improper Access Control Allows Employees to Auto-Approve Documents","id":"CVE-2026-24039"},"packages":[],"prev":{"headline":"Horilla HRM has XSS Bypass through Project Name","id":"CVE-2026-24037"},"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":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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-22","vendors":["horilla-opensource"]},"summary":"Attackers can bypass two-factor authentication in Horilla HRMS by omitting the OTP field, potentially compromising administrative accounts and sensitive HR data.","url":"https://insights.sbomify.com/CVE-2026-24038/"}