Vulnerability Description
Sync-in Server is an open-source platform for file storage, sharing, collaboration, and syncing. Prior to version 2.4.0, `POST /api/app/sync/register` accepts credentials and a TOTP code to register a desktop sync client. On a failed TOTP, `SyncClientsManager.register()` calls `updateAccesses(user, ip, false)`, which hits a freeze branch that writes `passwordAttempts` back unchanged. The counter never reaches `USER_MAX_PASSWORD_ATTEMPTS` (10) and the lockout gate never fires. A successful guess returns a `{clientId, clientToken}` pair. The token can be exchanged via `POST /api/app/sync/auth/cookie` for a full JWT. While the code is valid, the attacker can also call `POST /api/auth/2fa/disable` to permanently remove MFA. Version 2.4.0 patches the issue.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/Sync-in/server/security/advisories/GHSA-274f-6w77-8qm9
- https://github.com/Sync-in/server/security/advisories/GHSA-274f-6w77-8qm9
FAQ
What is CVE-2026-58271?
CVE-2026-58271 is a vulnerability with a CVSS score of 6.8 (MEDIUM). Sync-in Server is an open-source platform for file storage, sharing, collaboration, and syncing. Prior to version 2.4.0, `POST /api/app/sync/register` accepts credentials and a TOTP code to register a...
How severe is CVE-2026-58271?
CVE-2026-58271 has been rated MEDIUM with a CVSS base score of 6.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-58271?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.