VulnerabilityPublished 24 Mar 2026

CVE-2026-33330: error311 FileRise · Incorrect Authorization

Affects error311 FileRiseSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 3.10.0 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

7.1High

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: High
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: 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: 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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 24 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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 FileRise and error311/FileRise to 3.10.0.

Affected software

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

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

AI-suggested

The primary mitigation is to upgrade FileRise to version 3.10.0 or later, where the vulnerability is patched. Until upgrade is possible, organizations should restrict access to FileRise instances to trusted users only and enforce strict authentication and authorization policies. Review and limit read-only user permissions to minimize exposure. Network-level controls such as IP whitelisting or VPN access can reduce attack surface. Monitoring and logging of ONLYOFFICE save callback requests should be enabled to detect suspicious activity or unauthorized file modifications. Additionally, implement file integrity monitoring to detect unexpected changes. If possible, disable ONLYOFFICE integration temporarily until the patch is applied. Educate users about the risk of unauthorized file modifications and encourage reporting of anomalies. Regularly audit access logs and verify file integrity to identify potential exploitation attempts.

Description

CVE-2026-33330 is a high-severity broken access control vulnerability in FileRise versions prior to 3.10.0, specifically in its ONLYOFFICE integration. Authenticated users with read-only access can exploit this flaw to obtain a signed save callbackUrl and forge save callbacks, allowing them to overwrite files with malicious content. This vulnerability impacts confidentiality and integrity but does not affect availability. Exploitation requires authentication but no user interaction beyond that. The issue has been patched in version 3.10.0. Organizations using vulnerable FileRise versions should upgrade immediately and review access controls to mitigate risk.

Impact

This vulnerability allows authenticated users with only read permissions to escalate their privileges and modify files arbitrarily, compromising data integrity and potentially confidentiality if sensitive files are overwritten or replaced with malicious content. For organizations relying on FileRise for secure file management and collaboration, this can lead to unauthorized data tampering, loss of trust in document authenticity, and potential downstream impacts such as malware injection or data corruption. Since FileRise is self-hosted, organizations with exposed instances accessible over the network are at risk. The lack of availability impact means systems remain operational, but the integrity breach can have serious consequences for compliance, auditing, and operational security. Attackers exploiting this flaw could target sensitive documents, configuration files, or scripts, leading to broader compromise or lateral movement within the network.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
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.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (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 31 Mar 2026, 20:33 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats