{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-13375 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-13375 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-13375 is a medium-severity cross-site scripting vulnerability in Fortinet Fortianalyzer, published on 28 May 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-2018-13375 and fix it if it is affected.\n\nWhat it is: CVE-2018-13375 is a medium-severity cross-site scripting vulnerability in Fortinet Fortianalyzer, published on 28 May 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-2018-13375 in the wild and no public exploit code.\n\nAffected product: Fortinet Fortianalyzer. 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-2018-13375/ (Markdown: https://insights.sbomify.com/CVE-2018-13375/index.md)","id":"CVE-2018-13375","markdown":"https://insights.sbomify.com/CVE-2018-13375/index.md","name":"CVE-2018-13375","record":{"aliases":["GHSA-ffmh-82q7-w4gf"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet log management","requires_auth":"none","summary":"Attackers can inject malicious scripts via DHCP hostname parameters, leading to script execution when administrators view logs in FortiAnalyzer or FortiManager.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortianalyzer","vendor":"fortinet"},{"product":"fortimanager","vendor":"fortinet"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"An Improper Neutralization of Script-Related HTML Tags in Fortinet FortiAnalyzer 5.6.0 and below and FortiManager 5.6.0 and below allows an attacker to send DHCP request containing malicious scripts in the HOSTNAME parameter. The malicious script code is executed while viewing the logs in FortiAnalyzer and FortiManager (with FortiAnalyzer feature enabled).","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 FortiAnalyzer","id":"CVE-2018-13375","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"fortinet:fortianalyzer","products":["fortinet:fortianalyzer","fortinet:fortimanager"],"type":"xss","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in Fortinet FortiOS","id":"CVE-2018-13376"},"packages":[],"prev":{"headline":"Fortinet FortiOS and FortiADC Improper Access Control","id":"CVE-2018-13374"},"products":["FortiAnalyzer","FortiManager"],"published":"2019-05-28","related":[{"cvss_score":9.4,"headline":"Fortinet Multiple Products Authentication Bypass Using an Alternate Path or Channel","id":"CVE-2026-24858","kev_date_added":"2026-01-27","published":"2026-01-27"},{"cvss_score":9.3,"headline":"Memory corruption in FortiAnalyzer","id":"CVE-2023-25610","kev_date_added":null,"published":"2025-03-24"},{"cvss_score":8.8,"headline":"Server-side request forgery in Fortinet FortiAnalyzer, FortiManager","id":"CVE-2021-32603","kev_date_added":null,"published":"2021-08-05"},{"cvss_score":8.8,"headline":"Cross-site scripting in Fortinet FortiAnalyzer","id":"CVE-2020-12817","kev_date_added":null,"published":"2020-09-24"},{"cvss_score":8,"headline":"Auth bypass in FortiOS","id":"CVE-2024-48886","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":8,"headline":"Cross-site scripting in Fortinet FortiAnalyzer, FortiManager","id":"CVE-2022-39950","kev_date_added":null,"published":"2022-11-02"},{"cvss_score":7.8,"headline":"Command injection in Fortinet FortiManager, FortiAnalyzer, FortiPortal","id":"CVE-2021-26104","kev_date_added":null,"published":"2022-04-06"}],"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-10-25","vendors":["Fortinet"]},"summary":"Attackers can inject malicious scripts via DHCP hostname parameters, leading to script execution when administrators view logs in FortiAnalyzer or FortiManager.","url":"https://insights.sbomify.com/CVE-2018-13375/"}