# CVE-2025-64027: Snipe-IT has Cross-site Scripting vulnerability in CSV import workflow > Reflected XSS in Snipe-IT CSV import allows attackers to inject JavaScript via modified requests, potentially compromising admin sessions. - **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 20 Nov 2025 - **Updated:** 26 Nov 2025 - **Also known as:** GHSA-8x9v-8qgj-945x ## What is CVE-2025-64027? CVE-2025-64027 is a medium-severity cross-site scripting vulnerability in Snipeitapp Snipe-It, published on 20 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. ### Official description Snipe-IT v8.3.4 (build 20218) contains a reflected cross-site scripting (XSS) vulnerability in the CSV Import workflow. When an invalid CSV file is uploaded, the application returns a progress_message value that is rendered as raw HTML in the admin interface. An attacker can intercept and modify the POST /livewire/update request to inject arbitrary HTML or JavaScript into the progress_message. Because the server accepts the modified input without sanitization and reflects it back to the user, arbitrary JavaScript executes in the browser of any authenticated admin who views the import page. NOTE: this is disputed by the Supplier because the report only demonstrates that an authenticated user can choose to conduct a man-in-the-middle attack against himself. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2025-64027? 2 open source packages ship an affected version, including snipe/snipe-it. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `snipe/snipe-it` | Packagist | All versions to 8.3.4 | None | | `snipe/snipe-it` | Packagist | All versions to 8.3.4 | None | Products: Snipeitapp Snipe-It. ## How do I fix CVE-2025-64027? No fix has been published for CVE-2025-64027 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-64027 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64027 exists. Public exploit code: - Reflected Cross-Site Scripting in Snipe-IT CSV Import Workflow (github_poc): https://github.com/cybercrewinc/CVE-2025-64027 ## Other vulnerabilities in Snipeitapp Snipe-It - [CVE-2025-63601](https://insights.sbomify.com/CVE-2025-63601/): File upload in n/a (critical 9.9) - [CVE-2026-37709](https://insights.sbomify.com/CVE-2026-37709/): Snipe-IT has insecure permissions in file uploads (critical 9.8) - [CVE-2026-86738](https://insights.sbomify.com/CVE-2026-86738/): Snipe-IT before 8.7.0 CSS Injection via Custom CSS (critical 9.3) - [CVE-2026-116199](https://insights.sbomify.com/CVE-2026-116199/): Snipe-IT before 8.6.3 Authentication Bypass via Google SSO Callback (critical 9.2) - [CVE-2022-1380](https://insights.sbomify.com/CVE-2022-1380/): Stored Cross Site Scripting vulnerability in Item name parameter in snipe/snipe-it (critical 9.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-64027 and fix it if it is affected. What it is: CVE-2025-64027 is a medium-severity cross-site scripting vulnerability in Snipeitapp Snipe-It, published on 20 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. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64027 exists. Affected packages and fixed versions: - snipe/snipe-it (Packagist): affected all versions up to 8.3.4; no fix listed - snipe/snipe-it (Packagist): affected all versions up to 8.3.4; no fix listed Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-64027/ (Markdown: https://insights.sbomify.com/CVE-2025-64027/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64027 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64027 - OSV: https://osv.dev/vulnerability/CVE-2025-64027 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-64027/ Summaries are generated and may contain mistakes; the official description above is the record.