Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | The CVSS score of 4.1 with vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:N reflects a network-accessible vulnerability with low attack complexity but high privilege requirement, affecting system integrity across security boundaries. The vulnerability requires an authenticated user (PR:H), which significantly raises the operational bar compared to unauthenticated attacks. However, the real-world risk is elevated by several factors: the attack is completely automated with no user interaction required, the permission combination needed (PERM_REPLACE and PERM_LIST) is common in collaborative file systems, and the technical impact—unauthorized file deletion—causes irreversible data loss. The fact that this exploits a logical flaw in authorization logic rather than a cryptographic or protocol weakness means exploitation is straightforward once the API behavior is understood. Without KEV or EPSS data explicitly provided, the moderate CVSS score combined with the straightforward exploitation path and cross-boundary integrity impact suggests this merits prompt patching, particularly in multi-tenant or shared resource environments where such permission separation is critical. |
| Exploit ScenarioDerived | An authenticated user with PERM_REPLACE (permission to replace their own files) and PERM_LIST (permission to view other users' files) logs into the system, identifies a file belonging to another user through the list API, and crafts a replace request targeting that file with deleteNewFile set to true. Because the API endpoint fails to check whether the user possesses PERM_DELETE_OTHER_UPLOADS, the authorization check passes, and the target file is deleted. The attacker leaves no evidence of traditional deletion, as the file removal was processed through a replace operation. Multiple files can be deleted rapidly in sequence by automating requests against known file identifiers. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 13, 2026
An insufficient authorization check in a file replace API allows authenticated users with basic list and replace permissions to delete other users' files by abusing the deleteNewFile flag, bypassing the intended delete permission requirement. This affects any system implementing this vulnerable API pattern where permission checks are not properly enforced at the API endpoint level. While the CVSS score of 4.1 is moderate, the vulnerability requires high privilege level (authenticated user with PERM_REPLACE and PERM_LIST) and results in integrity impact through unauthorized file deletion across user boundaries.
RemediationAI
The primary remediation is to apply security patches from the affected system's vendor. Until patches are available, implement compensating controls by: (1) explicitly validating PERM_DELETE_OTHER_UPLOADS authorization before processing deleteNewFile flag in replace API calls, (2) enforcing permission checks at the API endpoint level rather than delegating to downstream logic, (3) restricting PERM_LIST and PERM_REPLACE permission grants to users who genuinely require them, and (4) implementing comprehensive audit logging on all file deletion operations to detect suspicious patterns. Organizations should also review similar file operation APIs (copy, move, rename) for equivalent authorization bypass vulnerabilities using the same permission model. Request the vendor security advisory with exact patched versions and upgrade timelines.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in go, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability exists in a file management API that implements a replace operation with a deleteNewFile flag parameter. The root cause is an authorization control bypass (CWE-863: Incorrect Authorization) where the API endpoint fails to validate whether the authenticated user possesses the PERM_DELETE permission before processing file deletion requests triggered through the replace operation. The affected system uses a permission model with discrete capabilities: PERM_REPLACE (modify own files), PERM_LIST (enumerate other users' uploads), PERM_DELETE (remove files), and PERM_DELETE_OTHER_UPLOADS (remove other users' files). The flaw stems from inadequate permission checks that do not verify PERM_DELETE_OTHER_UPLOADS when the deleteNewFile flag is set in replace requests targeting files outside the authenticated user's ownership scope.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:N
Primary rating from GitHub Advisory.
CVSS VectorGitHub Advisory
Lifecycle Timeline
2DescriptionGitHub Advisory
Summary
An insufficient authorization check in the file replace API allows a user with only list visibility permission (UserPermListOtherUploads) to delete another user's file by abusing the deleteNewFile flag, bypassing the requirement for UserPermDeleteOtherUploads.
Impact
Any authenticated user with PERM_REPLACE (replace own files) and PERM_LIST (view other users' uploads) can delete any other user's file without needing PERM_DELETE.
Executive ViewAI
Organizations using An insufficient authorization check in the file replace API should be aware of moderate risk from CVE-2026-30943, a incorrect authorization vulnerability rated CVSS 4.1. Attackers could gain access beyond their authorized level. Organizations should apply vendor updates when available and monitor for exploitation.
Apply vendor patch. If patching is delayed: restrict network access and enable monitoring.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-12075
GHSA-j6jp-78w8-34x6
NVD
CVE.org
EPSS
VulDB
Exploit-DB