{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-52331 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-52331 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-52331 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Nov 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-52331 and fix it if it is affected.\n\nWhat it is: CVE-2025-52331 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Nov 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-52331 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-2025-52331/ (Markdown: https://insights.sbomify.com/CVE-2025-52331/index.md)","id":"CVE-2025-52331","markdown":"https://insights.sbomify.com/CVE-2025-52331/index.md","name":"CVE-2025-52331","record":{"aliases":["GHSA-w8fm-xj22-4j56","UBUNTU-CVE-2025-52331"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WinRAR archive utility","requires_auth":"none","summary":"Attackers can inject malicious HTML into WinRAR reports to disclose user information like username and IP address when users open the report.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"winrar","vendor":"rarlab"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","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":"Cross-site scripting (XSS) vulnerability in the generate report functionality in Rarlab WinRAR 7.11, allows attackers to disclose user information such as the computer username, generated report directory, and IP address. The generate report command includes archived file names without validation in the HTML report, which allows potentially malicious HTML tags to be injected into the report. User interaction is required. User must use the \"generate report\" functionality and open the report.","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":"Cross-site scripting in n/a","id":"CVE-2025-52331","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-52335"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2025-52327"},"products":["n/a"],"published":"2025-11-12","related":[{"cvss_score":7.8,"headline":"RARLAB WinRAR Path Traversal","id":"CVE-2025-6218","kev_date_added":"2025-12-09","published":"2025-06-21"},{"cvss_score":7.8,"headline":"RARLAB WinRAR Code Execution","id":"CVE-2023-38831","kev_date_added":"2023-08-24","published":"2023-08-23"},{"cvss_score":7.8,"headline":"WinRAR Absolute Path Traversal","id":"CVE-2018-20250","kev_date_added":"2022-02-15","published":"2019-02-05"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-7144","kev_date_added":null,"published":"2009-09-01"},{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2004-1254","kev_date_added":null,"published":"2004-12-22"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2006-3845","kev_date_added":null,"published":"2006-07-25"},{"cvss_score":7.8,"headline":"RARLAB WinRAR Recovery Volume Improper Validation of Array Index Remote Code Execution Vulnerability","id":"CVE-2023-40477","kev_date_added":null,"published":"2024-05-03"}],"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-11-12","vendors":["n/a"]},"summary":"Attackers can inject malicious HTML into WinRAR reports to disclose user information like username and IP address when users open the report.","url":"https://insights.sbomify.com/CVE-2025-52331/"}