{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-39812 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-39812 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-39812 is a medium-severity cross-site scripting vulnerability in Fortinet Fortisandbox, published on 14 Apr 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-39812 and fix it if it is affected.\n\nWhat it is: CVE-2026-39812 is a medium-severity cross-site scripting vulnerability in Fortinet Fortisandbox, published on 14 Apr 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-39812 in the wild and no public exploit code.\n\nAffected product: Fortinet Fortisandbox. 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-2026-39812/ (Markdown: https://insights.sbomify.com/CVE-2026-39812/index.md)","id":"CVE-2026-39812","markdown":"https://insights.sbomify.com/CVE-2026-39812/index.md","name":"CVE-2026-39812","record":{"aliases":["GHSA-9q3x-6267-mffc"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet FortiSandbox","requires_auth":"high_privilege","summary":"An attacker can execute unauthorized code or commands via cross-site scripting in Fortinet FortiSandbox, requiring an upgrade to mitigate.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortisandbox","vendor":"fortinet"},{"product":"fortisandbox_cloud","vendor":"fortinet"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N/E:P/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"A improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Fortinet FortiSandbox 5.0.0 through 5.0.5, FortiSandbox 4.4.0 through 4.4.8, FortiSandbox 4.2 all versions, FortiSandbox PaaS 5.0.0 through 5.0.5, FortiSandbox PaaS 4.4.0 through 4.4.8, FortiSandbox PaaS 4.2 all versions may allow attacker to execute unauthorized code or commands via \u003cinsert attack vector here\u003e","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 FortiSandbox","id":"CVE-2026-39812","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"fortinet:fortisandbox","products":["fortinet:fortisandbox"],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in FortiSandbox","id":"CVE-2026-39813"},"packages":[],"prev":{"headline":"Integer overflow in FortiWeb","id":"CVE-2026-39811"},"products":["FortiSandbox","FortiSandbox PaaS"],"published":"2026-04-14","related":[{"cvss_score":9.1,"headline":"Fortinet FortiSandbox OS Command Injection","id":"CVE-2026-25089","kev_date_added":"2026-07-16","published":"2026-06-09"},{"cvss_score":9.1,"headline":"Fortinet FortiSandbox OS Command Injection","id":"CVE-2026-39808","kev_date_added":"2026-07-16","published":"2026-04-14"},{"cvss_score":9.1,"headline":"Missing authorization in FortiSandbox","id":"CVE-2026-26083","kev_date_added":null,"published":"2026-05-12"},{"cvss_score":9.1,"headline":"Path traversal in FortiSandbox","id":"CVE-2026-39813","kev_date_added":null,"published":"2026-04-14"},{"cvss_score":8.8,"headline":"SQL injection in Fortinet FortiSandbox","id":"CVE-2020-29011","kev_date_added":null,"published":"2021-08-04"},{"cvss_score":8.8,"headline":"Command injection in Fortinet FortiSandbox","id":"CVE-2021-26097","kev_date_added":null,"published":"2021-08-04"},{"cvss_score":8.6,"headline":"Command injection in FortiSandbox","id":"CVE-2024-52961","kev_date_added":null,"published":"2025-03-11"}],"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":"2026-04-14","vendors":["Fortinet"]},"summary":"An attacker can execute unauthorized code or commands via cross-site scripting in Fortinet FortiSandbox, requiring an upgrade to mitigate.","url":"https://insights.sbomify.com/CVE-2026-39812/"}