CVE-2026-30579
Received Received - Intake
Cross-Site Scripting in File Thingie 2.5.7 Upload Function

Publication date: 2026-03-20

Last updated on: 2026-04-01

Assigner: MITRE

Description
File Thingie 2.5.7 is vulnerable to Cross Site Scripting (XSS). A malicious user can leverage the "upload file" functionality to upload a file with a crafted file name used to trigger a Javascript payload.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-20
Last Modified
2026-04-01
Generated
2026-06-16
AI Q&A
2026-03-20
EPSS Evaluated
2026-06-14
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
leefish file_thingie 2.5.7
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

[{'type': 'paragraph', 'content': 'CVE-2026-30579 is a Cross Site Scripting (XSS) vulnerability affecting FileThingie version 2.5.7. It occurs through the "upload file" functionality, where a malicious user can upload a file with a specially crafted file name containing a JavaScript payload. When this file name is processed by the application, the JavaScript payload can be executed, leading to an XSS attack.'}] [1]

Impact Analysis

This vulnerability can have serious impacts including high confidentiality and integrity loss. An attacker can remotely execute malicious scripts in the context of the affected application, potentially stealing sensitive information, manipulating data, or performing actions on behalf of legitimate users. The attack requires low privileges and user interaction, and it has a low impact on availability.

Compliance Impact

I don't know

Detection Guidance

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by testing the "upload file" functionality of FileThingie version 2.5.7 for the ability to upload files with specially crafted file names containing JavaScript payloads.'}, {'type': 'paragraph', 'content': "One approach is to attempt uploading a file with a filename that includes typical XSS payloads such as <script>alert('XSS')</script> and then observe if the payload executes when the file name is rendered in the application."}, {'type': 'paragraph', 'content': 'Since this is a web application vulnerability, network detection commands are not directly applicable, but you can use web application testing tools or scripts to automate this process.'}, {'type': 'paragraph', 'content': 'For manual testing, you might use curl or wget to upload files with crafted names if the upload endpoint is accessible via HTTP requests.'}] [1]

Mitigation Strategies

Immediate mitigation steps include restricting or sanitizing file names during the upload process to prevent JavaScript or other executable code from being embedded.

Implement input validation and output encoding to neutralize any malicious payloads in file names.

If possible, upgrade or patch FileThingie to a version where this vulnerability is fixed.

Limit user privileges to reduce the risk of exploitation, as the vulnerability requires low privileges but user interaction.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-30579. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart