{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-35581 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-35581 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-35581 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 May 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-35581 and fix it if it is affected.\n\nWhat it is: CVE-2024-35581 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 May 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-35581 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-35581/ (Markdown: https://insights.sbomify.com/CVE-2024-35581/index.md)","id":"CVE-2024-35581","markdown":"https://insights.sbomify.com/CVE-2024-35581/index.md","name":"CVE-2024-35581","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Laboratory Management System","requires_auth":"none","summary":"Attackers can execute arbitrary web scripts via the Borrower Name field in the Laboratory Management System.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"computer_laboratory_management_system","vendor":"oretnom23"}],"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-94","name":"Improper Control of Generation of Code"}],"description":"A cross-site scripting (XSS) vulnerability in Sourcecodester Laboratory Management System v1.0 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the Borrower Name input field.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2024-35581","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-35582"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2024-35580"},"products":["n/a"],"published":"2024-05-28","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-34479","kev_date_added":null,"published":"2024-08-07"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-34480","kev_date_added":null,"published":"2024-08-07"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-31546","kev_date_added":null,"published":"2024-04-19"},{"cvss_score":9.4,"headline":"SQL injection in n/a","id":"CVE-2024-31545","kev_date_added":null,"published":"2024-04-22"},{"cvss_score":9.1,"headline":"SQL injection in n/a","id":"CVE-2024-31547","kev_date_added":null,"published":"2024-04-19"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2025-45956","kev_date_added":null,"published":"2025-04-29"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2024-54818","kev_date_added":null,"published":"2025-01-08"}],"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":"2025-02-13","vendors":["n/a"]},"summary":"Attackers can execute arbitrary web scripts via the Borrower Name field in the Laboratory Management System.","url":"https://insights.sbomify.com/CVE-2024-35581/"}