{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-13066 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-13066 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-13066 is a medium-severity cross-site scripting vulnerability in n/a, published on 29 Oct 2019. 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-2019-13066 and fix it if it is affected.\n\nWhat it is: CVE-2019-13066 is a medium-severity cross-site scripting vulnerability in n/a, published on 29 Oct 2019. 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-2019-13066 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-2019-13066/ (Markdown: https://insights.sbomify.com/CVE-2019-13066/index.md)","id":"CVE-2019-13066","markdown":"https://insights.sbomify.com/CVE-2019-13066/index.md","name":"CVE-2019-13066","record":{"aliases":["GHSA-4279-qvh5-v435"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Sahi Pro","requires_auth":"none","summary":"Reflected XSS in Sahi Pro allows attackers to execute arbitrary scripts via malicious input in script management fields.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sahi_pro","vendor":"sahipro"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","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":"Sahi Pro 8.0.0 has a script manager arena located at _s_/dyn/pro/DBReports with many different areas that are vulnerable to reflected XSS, by updating a script's Script Name, Suite Name, Base URL, Android, iOS, Scripts Run, Origin Machine, or Comment field. The sql parameter can be used to trigger reflected XSS.","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-2019-13066","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-13067"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2019-13063"},"products":["n/a"],"published":"2019-10-29","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2019-15102","kev_date_added":null,"published":"2019-09-06"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-13597","kev_date_added":null,"published":"2019-07-14"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2018-20469","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2018-20468","kev_date_added":null,"published":"2019-06-17"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2019-13063","kev_date_added":null,"published":"2019-09-23"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2018-20470","kev_date_added":null,"published":"2019-06-17"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Reflected XSS in Sahi Pro allows attackers to execute arbitrary scripts via malicious input in script management fields.","url":"https://insights.sbomify.com/CVE-2019-13066/"}