CVE-2026-82980: CWE-287 Improper Authentication - Generic in Nextcloud Files Lock
Any authenticated user can lock or unlock files they do not own by targeting absolute WebDAV paths of other users. The DAV plugin resolves files from the absolute request URI without verifying that the path segment matches the authenticated session user. This enables: Cross-user manual locks : attacker locks a victim's files, blocking writes (PUT/MOVE/DELETE, editor saves). Lock-token disclosure: the app returns the lock token to unauthorized callers, enabling them to remove token-based locks (client locks) of other users.
AI Analysis
Technical Summary
The vulnerability arises because the Nextcloud DAV plugin resolves file paths from the absolute request URI without confirming that the path segment corresponds to the authenticated session user. This flaw allows authenticated attackers to lock or unlock files belonging to other users by targeting absolute WebDAV paths. Additionally, the application returns lock tokens to unauthorized callers, which can be used to remove token-based locks set by other users. This improper authentication issue is tracked as CWE-287 and affects Nextcloud Files Lock versions from 31.0.0 up to and including 33.0.0.
Potential Impact
An attacker with valid authentication can interfere with other users' file operations by locking their files, preventing legitimate write operations such as PUT, MOVE, DELETE, or editor saves. The attacker can also obtain lock tokens for other users' files, enabling them to remove locks that rely on these tokens. This results in confidentiality, integrity, and availability impacts rated as low to medium severity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict authenticated user permissions where possible and monitor for unusual file lock activity. Avoid relying solely on lock tokens for access control.
CVE-2026-82980: CWE-287 Improper Authentication - Generic in Nextcloud Files Lock
Description
Any authenticated user can lock or unlock files they do not own by targeting absolute WebDAV paths of other users. The DAV plugin resolves files from the absolute request URI without verifying that the path segment matches the authenticated session user. This enables: Cross-user manual locks : attacker locks a victim's files, blocking writes (PUT/MOVE/DELETE, editor saves). Lock-token disclosure: the app returns the lock token to unauthorized callers, enabling them to remove token-based locks (client locks) of other users.
CVSS v3.0
Score 6.3medium
Affected software
Nextcloud
Files Lock
pkg:github/nextcloud/files-lockRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises because the Nextcloud DAV plugin resolves file paths from the absolute request URI without confirming that the path segment corresponds to the authenticated session user. This flaw allows authenticated attackers to lock or unlock files belonging to other users by targeting absolute WebDAV paths. Additionally, the application returns lock tokens to unauthorized callers, which can be used to remove token-based locks set by other users. This improper authentication issue is tracked as CWE-287 and affects Nextcloud Files Lock versions from 31.0.0 up to and including 33.0.0.
Potential Impact
An attacker with valid authentication can interfere with other users' file operations by locking their files, preventing legitimate write operations such as PUT, MOVE, DELETE, or editor saves. The attacker can also obtain lock tokens for other users' files, enabling them to remove locks that rely on these tokens. This results in confidentiality, integrity, and availability impacts rated as low to medium severity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict authenticated user permissions where possible and monitor for unusual file lock activity. Avoid relying solely on lock tokens for access control.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- hackerone
- Date Reserved
- 2026-08-31T15:00:00.543Z
- Cvss Version
- 3.0
- State
- PUBLISHED
Threat ID: 6aad953c55bf5e2cf577b92c
Added to database: 09/18/2026, 19:47:08 UTC
Last enriched: 09/18/2026, 20:02:15 UTC
Last updated: 09/18/2026, 22:34:46 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.