VulnerabilityPublished 1 Dec 2025

CVE-2025-66403: error311 FileRise · Cross-site Scripting

Affects error311 FileRiseSource CVE Database V5

Not known to be exploited · CVSS 4.6 Medium : upgrade to 2.2.3 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

4.6Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.2.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade error311/FileRise to 2.2.3.

Affected software

Product	Affected	Fixed in
GitHuberror311/FileRise`pkg:github/error311/FileRise`Other threats	Affected <2.2.3	Fixed in 2.2.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade FileRise to version 2.2.3 or later immediately to apply the official fix that sanitizes SVG uploads.
Implement strict file upload policies restricting SVG files or disallowing SVG uploads if not essential.
Use server-side content sanitization tools to strip scripts and event handlers from SVG files before storage or rendering.
Employ Content Security Policy (CSP) headers to restrict script execution and mitigate XSS impact if exploitation occurs.
Monitor file upload logs and user activities for suspicious SVG uploads or unusual behavior.
Educate users about the risks of uploading untrusted files and encourage cautious handling of file uploads.
Conduct regular security assessments and penetration testing focused on file upload functionalities.
Isolate the FileRise application environment to limit lateral movement in case of compromise.
Review and tighten authentication and authorization controls to minimize the number of users able to upload files.
Maintain up-to-date backups to recover quickly from any potential compromise.

Description

FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 2.2.3, a stored cross-site scripting (XSS) vulnerability exists in the Filerise application due to improper handling of uploaded SVG files. The application accepts user-supplied SVG uploads without sanitizing or restricting embedded script content. When a malicious SVG containing inline JavaScript or event-based payloads is uploaded, it is later rendered directly in the browser whenever viewed within the application. Because SVGs are XML-based and allow scripting, they execute in the origin context of the application, enabling full stored XSS. This vulnerability is fixed in 2.2.3.

Impact

For European organizations, this vulnerability can lead to unauthorized script execution within the FileRise application context, potentially compromising user sessions, stealing sensitive data, or performing unauthorized actions on behalf of users. Since FileRise is a self-hosted file manager, exploitation could allow attackers to pivot within internal networks or escalate privileges if the application is integrated with other systems. The impact is primarily on confidentiality and integrity, with no direct availability impact. Organizations handling sensitive or regulated data are at higher risk due to potential data leakage or manipulation. The requirement for authenticated upload and user interaction reduces the likelihood of widespread exploitation but does not eliminate targeted attacks. Industries such as finance, healthcare, and government agencies using FileRise for file management are particularly vulnerable. The medium severity rating suggests that while the threat is not critical, it warrants timely remediation to prevent exploitation. Failure to address this vulnerability could lead to reputational damage and compliance issues under European data protection regulations like GDPR.

Summary

CVE-2025-66403 is a stored cross-site scripting vulnerability identified in the FileRise web-based file manager before version 2.2.3. FileRise allows users to upload and manage files through a web interface, including SVG images. SVG files are XML-based and can embed JavaScript, which can be executed by browsers when the SVG is rendered. The vulnerability stems from FileRise's failure to sanitize or restrict embedded scripts within uploaded SVG files. An attacker with authenticated access can upload a crafted SVG containing malicious JavaScript payloads. When other users view the SVG within the application, the embedded script executes in the application's origin context, enabling full stored XSS. This can lead to session hijacking, unauthorized actions, or data theft within the scope of the application. The vulnerability requires user interaction to view the malicious SVG and privileges to upload files, limiting its exploitation scope. The CVSS 3.1 base score is 4.6, indicating medium severity due to the low impact on confidentiality and integrity, no availability impact, and the need for authentication and user interaction. No public exploits have been reported yet. The issue is resolved in FileRise version 2.2.3 by implementing proper sanitization or restrictions on SVG uploads to prevent script execution. Organizations using vulnerable versions should prioritize patching to mitigate risks.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
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.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Dec 2025, 23:16 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats