{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-7066 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-7066 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-7066 is a medium-severity cross-site scripting vulnerability in Jirafeau, published on 4 Jul 2025. 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-2025-7066 and fix it if it is affected.\n\nWhat it is: CVE-2025-7066 is a medium-severity cross-site scripting vulnerability in Jirafeau, published on 4 Jul 2025. 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-2025-7066 in the wild and no public exploit code.\n\nAffected product: Jirafeau. 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-2025-7066/ (Markdown: https://insights.sbomify.com/CVE-2025-7066/index.md)","id":"CVE-2025-7066","markdown":"https://insights.sbomify.com/CVE-2025-7066/index.md","name":"CVE-2025-7066","record":{"aliases":["GHSA-2fxj-q37f-g6jj"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Jirafeau file sharing","requires_auth":"none","summary":"Attackers can execute arbitrary scripts in victim browsers by bypassing MIME type checks during file preview in Jirafeau.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitLab","cpe":[{"product":"jirafeau","vendor":"jirafeau"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","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":"Jirafeau normally prevents browser preview for text files due to the possibility that for example SVG and HTML documents could be exploited for cross site scripting. This was done by storing the MIME type of a file and allowing only browser preview for MIME types beginning with image (except for image/svg+xml, see CVE-2022-30110 and CVE-2024-12326), video and audio. However, it was possible to bypass this check by sending a manipulated MIME type containing a comma and an other MIME type like text/html (for example image/png,text/html). Browsers see multiple MIME types and text/html would takes precedence, allowing a possible attacker to do a cross-site scripting attack. The check for MIME types was enhanced to prevent a browser preview when the stored MIME type contains a comma.","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":"Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Jirafeau","id":"CVE-2025-7066","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"HDF5 H5FScache.c H5FS__sinfo_serialize_node_cb heap-based overflow","id":"CVE-2025-7067"},"packages":[],"prev":{"headline":"Remote Code Execution via Unrestricted File Upload in PAD CMS","id":"CVE-2025-7065"},"products":["Jirafeau"],"published":"2025-07-04","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-11349","kev_date_added":null,"published":"2018-07-07"},{"cvss_score":6.1,"headline":"Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Jirafeau","id":"CVE-2026-1466","kev_date_added":null,"published":"2026-01-28"},{"cvss_score":6.1,"headline":"Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Jirafeau","id":"CVE-2024-12326","kev_date_added":null,"published":"2024-12-06"},{"cvss_score":6.1,"headline":"Cross-site Scripting in Jirafeau","id":"CVE-2022-30110","kev_date_added":null,"published":"2022-05-17"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-11350","kev_date_added":null,"published":"2018-07-07"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-11351","kev_date_added":null,"published":"2018-07-07"}],"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":"2025-09-16","vendors":["Jirafeau project"]},"summary":"Attackers can execute arbitrary scripts in victim browsers by bypassing MIME type checks during file preview in Jirafeau.","url":"https://insights.sbomify.com/CVE-2025-7066/"}