{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63307 exists.","fix":"No fix has been published for CVE-2025-63307 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-63307 is a high-severity cross-site scripting vulnerability in n/a, published on 6 Nov 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-63307 and fix it if it is affected.\n\nWhat it is: CVE-2025-63307 is a high-severity cross-site scripting vulnerability in n/a, published on 6 Nov 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63307 exists.\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-63307/ (Markdown: https://insights.sbomify.com/CVE-2025-63307/index.md)","id":"CVE-2025-63307","markdown":"https://insights.sbomify.com/CVE-2025-63307/index.md","name":"CVE-2025-63307","record":{"aliases":["GHSA-f9mp-xcq7-hf3m"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Laravel file manager","requires_auth":"high_privilege","summary":"Attackers can execute arbitrary scripts by uploading malicious HTML or SVG files due to insufficient validation in the Laravel file manager library.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"laravel_file_manager","vendor":"alexusmai"}],"cvss":{"score":8.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"alexusmai laravel-file-manager 3.3.1 is vulnerable to Cross Site Scripting (XSS). The application permits user-controlled upload, create, and rename of files to HTML and SVG types and serves those files inline without adequate content-type validation or output sanitization.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-10-25","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-10-25T15:34:17Z","kind":"github_poc","ref":"https://github.com/Theethat-Thamwasin/CVE-2025-63307","stars":1,"title":"An authenticated Stored Cross-site Scripting (XSS) vulnerability in laravel-file-manager v3.3.1 and below allows attackers with access to the file manager interface to inject and persist arbitrary JavaScript code in uploaded or created files. "}],"tier":"weaponised"},"has_fix":false,"headline":"Cross-site scripting in n/a","id":"CVE-2025-63307","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2025-63314"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2025-63298"},"products":["n/a"],"published":"2025-11-06","related":[{"cvss_score":9.1,"headline":"alexusmai laravel-file-manager is vulnerable to Directory Traversal via the unzip/extraction functionality","id":"CVE-2025-65346","kev_date_added":null,"published":"2025-12-04"},{"cvss_score":6.5,"headline":"alexusmai laravel-file-manager is vulnerable to Directory Traversal","id":"CVE-2025-65345","kev_date_added":null,"published":"2025-12-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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-11-06","vendors":["n/a"]},"summary":"Attackers can execute arbitrary scripts by uploading malicious HTML or SVG files due to insufficient validation in the Laravel file manager library.","url":"https://insights.sbomify.com/CVE-2025-63307/"}