Cross-board stack movement via mismatched permission identifier
Published May 20, 2022 · Updated Apr 22, 2025
Authorization bypass in Nextcloud Deck before 1.4.8, 1.5.0 through 1.5.5, and 1.6.0 allows remote authenticated users to alter other boards. StackService::update checks update permission using the supplied stack identifier where the destination board identifier is required. Any authenticated account can exploit this identifier confusion to move a stack and its existing cards from an owned board onto another user's board.
Summary
What happened
Authorization bypass in Nextcloud Deck before 1.4.8, 1.5.0 through 1.5.5, and 1.6.0 allows remote authenticated users to alter other boards. StackService::update checks update permission using the supplied stack identifier where the destination board identifier is required. Any authenticated account can exploit this identifier confusion to move a stack and its existing cards from an owned board onto another user's board.
The record
- CVE
- CVE-2022-29159
- Published
- May 20, 2022
- Updated
- Apr 22, 2025
- Vendor
- Nextcloud GmbH
- Product
- Security Advisories
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.4.8
- Affected versionversion=>= 1.5.0, < 1.5.6
- Affected versionversion== 1.6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- HackerOne proof-of-concept reportproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo