{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-47749 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-47749 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-47749 is a high-severity use after free vulnerability in FUJI ELECTRIC CO., LTD. V-SFT, published on 19 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-47749 and fix it if it is affected.\n\nWhat it is: CVE-2025-47749 is a high-severity use after free vulnerability in FUJI ELECTRIC CO., LTD. V-SFT, published on 19 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-47749 in the wild and no public exploit code.\n\nAffected product: FUJI ELECTRIC CO., LTD. V-SFT. 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-47749/ (Markdown: https://insights.sbomify.com/CVE-2025-47749/index.md)","id":"CVE-2025-47749","markdown":"https://insights.sbomify.com/CVE-2025-47749/index.md","name":"CVE-2025-47749","record":{"aliases":["GHSA-mr4j-xfv9-w967"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"V-SFT HMI software","requires_auth":"none","summary":"Attackers can execute arbitrary code or disclose information by tricking users into opening malicious V7 or V8 files in V-SFT software.","user_interaction":"required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[{"product":"monitouch_v-sft","vendor":"fujielectric"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-763","name":"Release of Invalid Pointer or Reference"},{"id":"CWE-761","name":"Free of Pointer not at Start of Buffer"}],"description":"V-SFT v6.2.5.0 and earlier contains an issue with free of pointer not at start of buffer in VS6EditData.dll!CWinFontInf::WinFontMsgCheck function. Opening specially crafted V7 or V8 files may lead to crash, information disclosure, and arbitrary code execution.","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":"Use after free in V-SFT","id":"CVE-2025-47749","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in V-SFT","id":"CVE-2025-47750"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2025-47748"},"products":["V-SFT"],"published":"2025-05-19","related":[{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-9659","kev_date_added":null,"published":"2017-08-14"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-9660","kev_date_added":null,"published":"2017-08-14"},{"cvss_score":8.5,"headline":"Fuji Electric Monitouch V-SFT Type Confusion","id":"CVE-2024-5597","kev_date_added":null,"published":"2024-06-10"},{"cvss_score":8.5,"headline":"Fuji Electric Monitouch V-SFT Stack-Based Buffer Overflow","id":"CVE-2024-34171","kev_date_added":null,"published":"2024-05-30"},{"cvss_score":8.5,"headline":"Fuji Electric Monitouch V-SFT Access of Resource Using Incompatible Type ('Type Confusion')","id":"CVE-2024-5271","kev_date_added":null,"published":"2024-05-30"},{"cvss_score":8.4,"headline":"Fuji Electric Monitouch V-SFT-6 Heap-based Buffer Overflow","id":"CVE-2025-54496","kev_date_added":null,"published":"2025-11-04"},{"cvss_score":8.4,"headline":"Fuji Electric Monitouch V-SFT-6 Stack-based Buffer Overflow","id":"CVE-2025-54526","kev_date_added":null,"published":"2025-11-04"}],"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-05-19","vendors":["FUJI ELECTRIC CO., LTD."]},"summary":"Attackers can execute arbitrary code or disclose information by tricking users into opening malicious V7 or V8 files in V-SFT software.","url":"https://insights.sbomify.com/CVE-2025-47749/"}