{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-30579 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-30579 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-30579 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-30579 and fix it if it is affected.\n\nWhat it is: CVE-2026-30579 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-30579 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-2026-30579/ (Markdown: https://insights.sbomify.com/CVE-2026-30579/index.md)","id":"CVE-2026-30579","markdown":"https://insights.sbomify.com/CVE-2026-30579/index.md","name":"CVE-2026-30579","record":{"aliases":["GHSA-gf2m-fvrm-3jx4"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"File Thingie","requires_auth":"low_privilege","summary":"A malicious user can execute arbitrary JavaScript via a crafted file name in the upload functionality of File Thingie.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"file_thingie","vendor":"leefish"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"File Thingie 2.5.7 is vulnerable to Cross Site Scripting (XSS). A malicious user can leverage the \"upload file\" functionality to upload a file with a crafted file name used to trigger a Javascript payload.","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-2026-30579","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2026-30580"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2026-30578"},"products":["n/a"],"published":"2026-03-20","related":[{"cvss_score":9.4,"headline":"File Thingie 2.5.7 Authenticated Arbitrary File Upload Remote Code Execution","id":"CVE-2023-53942","kev_date_added":null,"published":"2025-12-18"},{"cvss_score":9.3,"headline":"FileThingie 2.5.7 Arbitrary File Upload via ft2.php","id":"CVE-2019-25471","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":6.5,"headline":"Cross-site scripting in n/a","id":"CVE-2026-30578","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":4.3,"headline":"Path traversal in n/a","id":"CVE-2026-30580","kev_date_added":null,"published":"2026-03-20"}],"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-03-23","vendors":["n/a"]},"summary":"A malicious user can execute arbitrary JavaScript via a crafted file name in the upload functionality of File Thingie.","url":"https://insights.sbomify.com/CVE-2026-30579/"}