VulnerabilityPublished 9 Feb 2026

CVE-2026-25231: error311 FileRise · Improper Access Control

Affects error311 FileRiseSource CVE Database V5

Not known to be exploited · public detection template (Nuclei) · CVSS 7.5 High : upgrade to 3.3.0 soon.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 1.7% chance of exploitation in 30 days – higher than 77% 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:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within 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 9 Feb 2026
Detectable: evidence found.
nuclei template: FileRise <= 3.3.0 - Unauthenticated File Read
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 FileRise installations to version 3.3.0 or later, where the vulnerability is patched. Until upgrades can be applied, administrators should implement strict network-level access controls to restrict access to the /uploads directory, such as IP whitelisting or VPN-only access. Web server configurations (e.g., Apache, Nginx) can be adjusted to deny direct access to the /uploads path or require authentication before serving files. Regular audits of uploaded files should be conducted to identify and remove any sensitive data that may have been exposed. Organizations should also monitor web server logs for suspicious access patterns indicating attempts to enumerate or access files in the uploads directory. Implementing comprehensive file upload validation and access control policies will help prevent similar issues. Finally, raising user awareness about secure file handling and ensuring that sensitive data is not uploaded without encryption or additional protections can reduce risk.

Description

CVE-2026-25231 is a high-severity vulnerability in FileRise versions prior to 3.3.0, a self-hosted web file manager and WebDAV server. The flaw arises from improper access control on the /uploads directory, allowing unauthenticated users to read files if they know or guess the file path. This can lead to exposure of sensitive data and privacy breaches without requiring any authentication or user interaction. The vulnerability does not impact integrity or availability but poses a significant confidentiality risk. It is fixed in version 3.3.0. European organizations using vulnerable versions of FileRise should prioritize upgrading to mitigate potential data leaks.

Impact

For European organizations, this vulnerability poses a significant risk of sensitive data exposure, especially for entities that use FileRise to manage confidential or regulated information. Data leaks could lead to privacy violations, regulatory non-compliance (e.g., GDPR), reputational damage, and potential financial penalties. Since the vulnerability allows unauthenticated remote access to uploaded files, attackers could harvest sensitive documents, intellectual property, or personally identifiable information without detection. This risk is heightened for sectors such as healthcare, finance, legal, and government agencies that often handle sensitive data and may use self-hosted file management solutions. The lack of integrity or availability impact means the threat is primarily data confidentiality loss, but this alone can have severe consequences under European data protection laws. Organizations with public-facing FileRise instances are particularly vulnerable, as attackers do not need credentials or user interaction to exploit the flaw.

CWE-284Improper Access Control (opens in a new tab)
Pillar weaknessCWE Top 25 (2025): #19OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Embedding Scripts within Scripts (opens in a new tab)
Modification of Windows Service Configuration (opens in a new tab)
Malicious Root Certificate (opens in a new tab)
Intent Spoof (opens in a new tab)
WebView Exposure (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-552Files or Directories Accessible to External Parties (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product makes files or directories accessible to unauthorized actors, even though they should not be.
Implementation · System Configuration · Operation
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to disable public access.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.5.1 (opens in a new tab)
V12.4.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
Attack patterns
Collect Data from Common Resource Locations (opens in a new tab)
Probe System Files (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

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-284, CWE-552

Technical details

References

Community reviews

Related threats