Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-80208 – Authentication Bypass / Unauthorized Account Enumeration & Closure – APITable throu

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-80208 is a missing-authentication vulnerability (CWE-306) in APITable, an open-source API-oriented low-code platform. Two internal endpoints in InternalUserController are exposed without authentication, letting an unauthenticated network attacker enumerate accounts pending deletion and permanently close them, bypassing the 30-day recovery window. The issue carries a CVSS score of 8.8 (High).

Technical details

  • Root cause: getUserHistories and closePausedUserAccount in InternalUserController are annotated with requiredLogin = false, so APITable’s ResourceInterceptor returns before any session or API key check runs.
  • Trigger condition: the nginx gateway shipped with the product proxies every /api request to the backend, making both "internal" endpoints reachable from any client that can reach the gateway — no internal-network restriction is enforced.
  • Attack vector: network, no privileges or user interaction required. An attacker sends a POST to /api/v1/internal/getUserHistories to enumerate accounts sitting in the 30-day post-deletion cooling-off period, then POSTs to /api/v1/internal/users/{userId}/close for each one.
  • Impact: the closure call clears the account’s email, phone number and nickname, cancels its space subscriptions, removes its space memberships, and deletes its OAuth bindings — permanently destroying the account and defeating the intended recovery window, with no way for the legitimate owner to reverse it.

Affected software

  • apitable/apitable: all versions through 1.13.0-beta.1

Severity

  • CVSS v4.0: 8.8 (High) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1: 8.2 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

Mitigation and recommended actions

  • Immediate: No official patched release has been published by the vendor at this time. Monitor the APITable GitHub repository for a fix and upgrade as soon as one is available.
  • Workarounds/network mitigations: Restrict network access to internal API routes (/api/v1/internal/*) at the gateway or firewall so they cannot be reached from outside the trusted backend network; do not expose the nginx gateway’s /api proxy to untrusted clients without additional access controls; consider adding authentication (e.g., a shared secret) in front of internal-only endpoints until an upstream fix is released.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: APITable
  • Raw response body: "IS_APITABLE": true, Powered by APITable

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge