{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-46235 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-46235 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-46235 is a medium-severity cross-site scripting vulnerability in fogproject, published on 31 Oct 2023. 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-46235 and fix it if it is affected.\n\nWhat it is: CVE-2023-46235 is a medium-severity cross-site scripting vulnerability in fogproject, published on 31 Oct 2023. 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-46235 in the wild and no public exploit code.\n\nAffected product: fogproject. 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-46235/ (Markdown: https://insights.sbomify.com/CVE-2023-46235/index.md)","id":"CVE-2023-46235","markdown":"https://insights.sbomify.com/CVE-2023-46235/index.md","name":"CVE-2023-46235","record":{"aliases":["GHSA-cvf7-7mvq-5694"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"FOG imaging suite","requires_auth":"none","summary":"Attackers can inject malicious scripts into FOG server logs, which execute when administrators view the log dashboard, potentially leading to account takeover.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"fogproject","vendor":"fogproject"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-80","name":"Improper Neutralization of Script-Related HTML Tags in a Web Page"},{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"FOG is a free open-source cloning/imaging/rescue suite/inventory management system. Prior to version 1.5.10.15, due to a lack of request sanitization in the logs, a malicious request containing XSS would be stored in a log file. When an administrator of the FOG server logged in and viewed the logs, they would be parsed as HTML and displayed accordingly. Version 1.5.10.15 contains a patch. As a workaround, view logs from an external text editor rather than the dashboard.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"FOG stored XSS on log screen via unsanitized request logging","id":"CVE-2023-46235","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"FOG SSRF via unauthenticated endpoint(s)","id":"CVE-2023-46236"},"packages":[],"prev":{"headline":"browserify-sign vulnerable via an upper bound check issue in `dsaVerify` that leads to a signature forgery attack","id":"CVE-2023-46234"},"products":["fogproject"],"published":"2023-10-31","related":[{"cvss_score":9.9,"headline":"FOG's authentication bypass leads to full SQL DB dump","id":"CVE-2025-58443","kev_date_added":null,"published":"2025-09-06"},{"cvss_score":9.8,"headline":"FOG has a command injection in /fog/management/export.php?filename=","id":"CVE-2024-39914","kev_date_added":null,"published":"2024-07-12"},{"cvss_score":9.3,"headline":"FOG leaks sensitive information (AD domain, username and password)","id":"CVE-2024-42348","kev_date_added":null,"published":"2024-08-02"},{"cvss_score":8.8,"headline":"FOG Authenticated File Upload RCE","id":"CVE-2024-40645","kev_date_added":null,"published":"2024-07-31"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2021-32243","kev_date_added":null,"published":"2021-06-16"},{"cvss_score":8.6,"headline":"FOG SSRF via unauthenticated endpoint(s)","id":"CVE-2023-46236","kev_date_added":null,"published":"2023-10-31"},{"cvss_score":8.2,"headline":"Missing authorization in fogproject","id":"CVE-2026-47688","kev_date_added":null,"published":"2026-07-21"}],"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-09-05","vendors":["FOGProject"]},"summary":"Attackers can inject malicious scripts into FOG server logs, which execute when administrators view the log dashboard, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2023-46235/"}