{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2023-5378 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-5378 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-5378 is a high-severity cross-site scripting vulnerability in Jan Syski MegaBIP, published on 29 Jan 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-2023-5378 and fix it if it is affected.\n\nWhat it is: CVE-2023-5378 is a high-severity cross-site scripting vulnerability in Jan Syski MegaBIP, published on 29 Jan 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-2023-5378 in the wild and no public exploit code.\n\nAffected product: Jan Syski MegaBIP. 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-2023-5378/ (Markdown: https://insights.sbomify.com/CVE-2023-5378/index.md)","id":"CVE-2023-5378","markdown":"https://insights.sbomify.com/CVE-2023-5378/index.md","name":"CVE-2023-5378","record":{"aliases":["GHSA-9w3h-593p-q56r"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"BIP web application","requires_auth":"none","summary":"Stored XSS in MegaBIP allows attackers to inject malicious scripts, potentially leading to session hijacking or code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[{"product":"megabip","vendor":"megabip"},{"product":"smodbip","vendor":"smod"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Improper Input Validation vulnerability in  MegaBIP and already unsupported SmodBIP software allows for Stored XSS.This issue affects SmodBIP in all versions and MegaBIP in versions up to 4.36.2. MegaBIP 5.08 was tested and is not vulnerable. A precise range of vulnerable versions remains unknown.","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":"Stored XSS in SmodBIP and MegaBIP","id":"CVE-2023-5378","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Undertow: ajp request closes connection exceeding maxrequestsize","id":"CVE-2023-5379"},"packages":[],"prev":{"headline":"Out-of-bounds Read in gpac/gpac","id":"CVE-2023-5377"},"products":["MegaBIP","SmodBIP"],"published":"2024-01-29","related":[{"cvss_score":9.3,"headline":"SQL Injection in MegaBIP","id":"CVE-2024-1576","kev_date_added":null,"published":"2024-06-12"},{"cvss_score":9.3,"headline":"Remote Code Execution in MegaBIP","id":"CVE-2024-1577","kev_date_added":null,"published":"2024-06-12"},{"cvss_score":9.3,"headline":"Arbitrary File Upload in MegaBIP","id":"CVE-2024-1659","kev_date_added":null,"published":"2024-06-12"}],"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":"2025-06-17","vendors":["Jan Syski"]},"summary":"Stored XSS in MegaBIP allows attackers to inject malicious scripts, potentially leading to session hijacking or code execution.","url":"https://insights.sbomify.com/CVE-2023-5378/"}