{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-27477 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-27477 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-27477 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-27477 and fix it if it is affected.\n\nWhat it is: CVE-2024-27477 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-27477 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2024-27477/ (Markdown: https://insights.sbomify.com/CVE-2024-27477/index.md)","id":"CVE-2024-27477","markdown":"https://insights.sbomify.com/CVE-2024-27477/index.md","name":"CVE-2024-27477","record":{"aliases":["GHSA-fw35-8hjm-jw2p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Leantime project management","requires_auth":"none","summary":"Attackers can inject malicious JavaScript into ticket titles, enabling stored XSS and potential SSRF attacks in Leantime.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"leantime","vendor":"leantime"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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":"In Leantime 3.0.6, a Cross-Site Scripting vulnerability exists within the ticket creation and modification functionality, allowing attackers to inject malicious JavaScript code into the title field of tickets (also known as to-dos). This stored XSS vulnerability can be exploited to perform Server-Side Request Forgery (SSRF) attacks.","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":"Cross-site scripting in n/a","id":"CVE-2024-27477","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"File upload in n/a","id":"CVE-2024-27480"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-27476"},"products":["n/a"],"published":"2024-04-10","related":[{"cvss_score":8.9,"headline":"Leantime Stored Cross-site Scripting Vulnerability","id":"CVE-2023-33961","kev_date_added":null,"published":"2023-05-30"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2024-27474","kev_date_added":null,"published":"2024-04-10"},{"cvss_score":8.7,"headline":"Time-based blind injection in Leantime","id":"CVE-2020-5292","kev_date_added":null,"published":"2020-03-31"},{"cvss_score":7.6,"headline":"Cross-site scripting in n/a","id":"CVE-2024-27705","kev_date_added":null,"published":"2024-04-03"},{"cvss_score":6.5,"headline":"Authenticated SQL Injection in leantime","id":"CVE-2023-45826","kev_date_added":null,"published":"2023-10-19"},{"cvss_score":5.4,"headline":"Leantime affected by Improper Neutralization of HTML Tags","id":"CVE-2025-28254","kev_date_added":null,"published":"2025-03-28"}],"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":"partial"},"state":"PUBLISHED","updated":"2024-11-06","vendors":["n/a"]},"summary":"Attackers can inject malicious JavaScript into ticket titles, enabling stored XSS and potential SSRF attacks in Leantime.","url":"https://insights.sbomify.com/CVE-2024-27477/"}