{
  "id": "CVE-2026-58269",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-58269",
  "published_at": "2026-09-21T20:01:56.322Z",
  "title": "Sync-in Server has a complete 2FA Bypass via `POST /api/auth/token`",
  "vendor": "Sync-in",
  "product": "server",
  "cvss": {
    "score": 8.1,
    "source": "cna",
    "vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "Sync-in Server is an open-source platform for file storage, sharing, collaboration, and syncing. Prior to version 2.4.0, `POST /api/auth/token` authenticates with username and password only, then calls `getTokens()`, which returns full access and refresh JWTs without checking whether the account has TOTP 2FA enabled. An attacker with stolen or phished credentials can bypass 2FA in a single request. The parallel login endpoint (`POST /api/auth/login`) correctly enforces 2FA by calling `setCookies(user, res, true)`, which gates on `user.twoFaEnabled`. Version 2.4.0 patches the issue.",
  "cwe": "CWE-288",
  "cvss_by_source": {
    "cna": 8.1
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Sync-in",
        "product": "server",
        "ranges": [
          "\u003c 2.4.0"
        ],
        "fixed_in": [
          "2.4.0"
        ]
      }
    ],
    "upgrade": [
      "Upgrade server to 2.4.0 or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/Sync-in/server/security/advisories/GHSA-92cr-jxw4-5wjg"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
