VulnerabilityPublished 9 Feb 2026

CVE-2026-25230: error311 FileRise · Cross-site Scripting

Affects error311 FileRiseSource CVE Database V5

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

Data as of 26 Oct 2026, 17:16 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 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.3.0

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

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

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: None: There is no loss of confidentiality within 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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Feb 2026
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 3.3.0.

Affected software

Product	Affected	Fixed in
error311FileRise	Affected <3.3.0	Fixed in 3.3.0

AI-suggested

European organizations should immediately upgrade all FileRise instances to version 3.3.0 or later to remediate this vulnerability. Until upgrades are completed, implement strict access controls to limit authenticated user privileges, ensuring only trusted users have write or administrative access. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious HTML injection attempts. Conduct regular audits of user accounts and session activities to identify unusual behavior. Additionally, educate users about the risks of interacting with unexpected or suspicious interface elements, emphasizing caution with links and forms within the application. Consider network segmentation to isolate FileRise servers from broader enterprise networks, reducing the risk of lateral movement if an account is compromised.

Description

CVE-2026-25230 is a medium severity cross-site scripting (XSS) vulnerability affecting FileRise versions prior to 3.3.0. It allows an authenticated user to inject HTML elements into the web interface, potentially modifying the DOM to include malicious forms or links that could redirect users or trigger unwanted actions upon interaction. Exploitation requires authentication and user interaction, limiting its impact to users with access to the system. The vulnerability does not compromise confidentiality but can affect integrity and availability by manipulating the web interface. This issue has been fixed in FileRise version 3.3.0. European organizations using vulnerable versions should prioritize upgrading and implement strict access controls to mitigate risks.

Impact

For European organizations, this vulnerability poses a moderate risk primarily to the integrity and availability of the FileRise web interface. Since exploitation requires authenticated access, the threat is mostly internal or from compromised accounts. Attackers could manipulate the web interface to trick users into performing unintended actions, potentially leading to data manipulation or denial of service within the application. While confidentiality is not directly impacted, the altered interface could facilitate social engineering attacks or indirect data exposure. Organizations relying on FileRise for file management or WebDAV services could face operational disruptions or reduced trust in the system's integrity. The impact is heightened in environments with multiple users sharing access or where user privileges are not tightly controlled.

Summary

CVE-2026-25230 is an HTML Injection vulnerability classified under CWE-79 (Improper Neutralization of Input During Web Page Generation) and CWE-116 (Improper Encoding or Escaping of Output). It affects FileRise, a self-hosted web file manager and WebDAV server, in versions prior to 3.3.0. The vulnerability allows an authenticated user to inject arbitrary HTML elements into the Document Object Model (DOM) of the web interface. This can include form elements that interact with backend endpoints or link elements that redirect users upon clicking. Because the vulnerability requires authentication and user interaction, exploitation is limited to users who already have some level of access to the system. The injected content can be used to manipulate the user interface, potentially leading to actions like phishing within the application, session manipulation, or triggering unintended requests. The CVSS v3.1 score is 4.6 (medium severity), reflecting the limited scope and impact. The vulnerability was publicly disclosed on February 9, 2026, and has been addressed in FileRise version 3.3.0. No known exploits are reported in the wild at this time.

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).
CWE-116Improper Encoding or Escaping of Output (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
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.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Implementation
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.
OWASP Cheat Sheets
Content Security Policy (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
Query Parameterization (opens in a new tab)
OWASP ASVS 4.0.3
V14.4.6 (opens in a new tab)
V14.4.4 (opens in a new tab)
V14.4.2 (opens in a new tab)
Attack patterns
Cross Zone Scripting (opens in a new tab)
User-Controlled Filename (opens in a new tab)
Web Server Logs Tampering (opens in a new tab)
AJAX Footprinting (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 17 Feb 2026, 09:43 UTC

WeaknessesCWE-79, CWE-116

Technical details

References

Community reviews

Related threats