CVE-2026-30578
Cross-Site Scripting in File Thinghie 2.5.7 via dir Parameter
Publication date: 2026-03-20
Last updated on: 2026-04-01
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| leefish | file_thingie | 2.5.7 |
Helpful Resources
Exploitability
| 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 Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-30578 is a Cross Site Scripting (XSS) vulnerability found in FileThingie version 2.5.7. It occurs because the application improperly handles the "dir" parameter in GET requests, allowing a malicious user to inject and execute arbitrary JavaScript code within the context of the affected web application.'}] [1]
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': "This vulnerability can have a significant impact as it allows attackers to execute arbitrary JavaScript code in the context of the victim's browser. According to the CVSS vector, it is network exploitable with low attack complexity and requires low privileges and user interaction. The impact includes high confidentiality and integrity loss, meaning attackers could steal sensitive information or manipulate data, and a low impact on availability."}] [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by monitoring HTTP GET requests to the FileThingie 2.5.7 application, specifically looking for the "dir" parameter containing suspicious or arbitrary JavaScript code.'}, {'type': 'paragraph', 'content': 'A practical approach is to use tools like curl or wget to send crafted GET requests with JavaScript payloads in the "dir" parameter and observe if the response reflects the injected code, indicating vulnerability.'}, {'type': 'list_item', 'content': 'Example curl command to test for XSS: curl -i "http://target/filethingie/?dir=<script>alert(\'XSS\')</script>"'}, {'type': 'list_item', 'content': 'Use web vulnerability scanners or proxy tools (e.g., Burp Suite) to automate detection of reflected XSS in the "dir" parameter.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'Immediate mitigation steps include applying input validation and sanitization on the "dir" parameter to prevent injection of arbitrary JavaScript code.'}, {'type': 'paragraph', 'content': 'If a patch or updated version of FileThingie addressing this vulnerability is available, upgrade to that version promptly.'}, {'type': 'paragraph', 'content': 'As a temporary measure, consider implementing Web Application Firewall (WAF) rules to block requests containing suspicious scripts in the "dir" parameter.'}, {'type': 'paragraph', 'content': 'Limit user privileges and monitor logs for suspicious activity related to the "dir" parameter.'}] [1]