VulnerabilityPublished 15 Jan 2026Updated 16 Jan 2026

CVE-2025-67077: Unrestricted File Upload

Source CVE Database V5

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

8.8High

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

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

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

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

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: 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: 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: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Jan 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

AI-suggested

Immediate mitigation steps include: 1) Monitoring Omnispace Agora Project vendor communications for official patches and applying them promptly once available. 2) Implementing strict access controls to restrict file upload functionality to trusted authenticated users only, and disabling guest upload capabilities if possible. 3) Employing robust file validation mechanisms, including whitelisting allowed file types, scanning uploads for malware, and enforcing size limits. 4) Using web application firewalls (WAFs) to detect and block suspicious upload attempts targeting the UploadTmpFile action. 5) Conducting thorough security audits and penetration testing focused on file upload functionalities. 6) Isolating the application environment to limit the impact of potential compromise, such as running the service in containers or sandboxed environments. 7) Enhancing logging and monitoring to detect anomalous upload activities promptly. 8) Educating administrators and users about the risks and signs of exploitation. These measures go beyond generic advice by focusing on the specific vulnerable action and the conditions under which guest users may exploit the vulnerability.

Description

CVE-2025-67077 is a high-severity file upload vulnerability affecting Omnispace Agora Project versions before 25.10. It allows authenticated users, and under certain conditions guest users, to upload files via the UploadTmpFile action without sufficient validation. This vulnerability can lead to full compromise of confidentiality, integrity, and availability of affected systems. Exploitation requires low attack complexity and no user interaction, making it highly dangerous. Although no known exploits are currently in the wild, the vulnerability's characteristics suggest a significant risk if weaponized. European organizations using Omnispace Agora Project are at risk, especially those with exposed or internet-facing instances. Mitigation requires immediate patching once available and implementing strict file upload validation and access controls. Countries with higher adoption of Omnispace Agora Project and critical infrastructure reliance on it are most likely to be targeted. Due to the high impact and ease of exploitation, this vulnerability demands urgent attention from defenders.

Impact

For European organizations, this vulnerability poses a severe threat, especially those using Omnispace Agora Project in critical sectors such as telecommunications, government, finance, and infrastructure. Successful exploitation can lead to unauthorized access to sensitive data, disruption of services, and potential ransomware deployment. The ability for guest users to exploit the vulnerability under certain conditions increases the risk of external attackers gaining foothold without authentication. This can result in data breaches, loss of customer trust, regulatory penalties under GDPR, and operational downtime. Organizations with internet-facing Omnispace Agora Project instances are particularly vulnerable. The high severity score indicates that the confidentiality, integrity, and availability of systems can be fully compromised, potentially affecting large-scale deployments and interconnected systems across European networks.

Summary

CVE-2025-67077 is a file upload vulnerability classified under CWE-434 affecting Omnispace Agora Project versions prior to 25.10. The vulnerability arises from insufficient validation and sanitization of files uploaded via the UploadTmpFile action. Authenticated users can exploit this flaw to upload arbitrary files, and under certain conditions, even guest users may exploit it. The vulnerability allows attackers to upload malicious files, potentially leading to remote code execution, data exfiltration, or system compromise. The CVSS 3.1 base score is 8.8, reflecting high impact on confidentiality, integrity, and availability (C:H/I:H/A:H), with network attack vector (AV:N), low attack complexity (AC:L), requiring privileges (PR:L), and no user interaction (UI:N). The scope is unchanged (S:U), indicating the vulnerability affects the same security scope. No patches are currently linked, and no known exploits have been reported in the wild as of the publication date. However, the vulnerability's nature makes it a prime candidate for exploitation once weaponized. The UploadTmpFile action likely handles temporary file uploads, and improper controls can allow attackers to upload web shells or other malicious payloads. This can lead to full system compromise, lateral movement, or persistent access. The vulnerability is particularly dangerous because it can be exploited remotely over the network with minimal prerequisites, increasing the attack surface significantly.

CWE-434Unrestricted Upload of File with Dangerous Type (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #12OWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
Architecture and Design
Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Architecture and Design
Consider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Web Service Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
File Upload (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V12.5.2 (opens in a new tab)
V13.1.5 (opens in a new tab)
V12.2.1 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (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

Description

AI analysisMachine-generated, updated 22 Jan 2026, 21:27 UTC

WeaknessesCWE-434

Technical details

References

Community reviews

Related threats