CVE-2026-80208
HighCVSS 8.2Exploitation Probability (EPSS)
Low risk24th percentile - higher than 24% of all known CVEs
Summary
APITable through 1.13.0-beta.1 annotates both getUserHistories and closePausedUserAccount with requiredLogin = false. ResourceInterceptor honors that annotation by returning before any session or API key is validated, and the nginx gateway proxies every /api request to the backend. An unauthenticated attacker can enumerate accounts in the cooling-off period and close them, deleting account data and preventing recovery.
Risk Assessment
Unauthorized account closure may lead to data loss and system integrity compromise.
Recommendation
Upgrade APITable to a version after 1.13.0-beta.1 that requires authentication for these endpoints.
Other vulnerabilities in APITable
See all- CVE-2026-111344Medium
APITable through 1.14.0-beta contains an authorization bypass vulnerability that allows authenticated users to read node descriptions from other spaces by supplying a user-controlled nodeId. Attackers can request GET /node/{nodeId}/description, which skips space membership and node permission checks, to disclose cross-tenant datasheet, folder, and form descriptions.
- CVE-2026-86120Medium
APITable through 1.13.0-beta.1 contains an incorrect authorization vulnerability in NodePermissionGuard that fails to enforce node-level access control when permission lookups throw exceptions. Attackers with valid Fusion API tokens can write attachments to private datasheets they have been explicitly denied access to by exploiting the unhandled exception in the permission guard.
- CVE-2026-84485High
APITable through version 1.13.0-beta.1 exposes the internal organization loadOrSearch endpoint without authentication, allowing unauthenticated attackers to retrieve member names, email addresses, and team hierarchy. Attackers can query the endpoint with space identifiers obtained from shared links or public templates to enumerate the complete member directory of any workspace.
- CVE-2026-80207Medium
Vulnerability in APITable up to 1.13.0-beta.1 allows an unauthenticated attacker to create notifications in the system. Missing required login for the create handler of InternalNotifyController and nginx proxy allow access to the API.
Original NVD description (English source)
APITable through 1.13.0-beta.1 annotates both getUserHistories and closePausedUserAccount in InternalUserController with requiredLogin = false. ResourceInterceptor honours that annotation by returning before any session or API key is validated, and the nginx gateway shipped with the product proxies every /api request to the backend server, so both endpoints are reachable by any unauthenticated client that can reach the gateway. An attacker can POST to /api/v1/internal/getUserHistories to enumerate the accounts sitting in the 30-day cooling-off period that follows a deletion request, then POST to /api/v1/internal/users/{userId}/close for each one. The closure path clears the account's email address, phone number and nickname, cancels its space subscriptions, removes its space memberships and deletes its OAuth bindings, so the cooling-off window that exists to let a user reverse a deletion request is bypassed and the account cannot be recovered.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS