Summary
APITable through version 1.13.0-beta.1 exposes an internal organization loadOrSearch endpoint without authentication. An unauthenticated attacker who obtains a workspace identifier may enumerate member names, email addresses, and team hierarchy, creating a significant privacy and reconnaissance risk.
Affected context
The vulnerability occurs in APITable deployments where the internal organization directory endpoint is reachable without an authentication check. Workspaces may be exposed when identifiers can be obtained from shared links, public templates, or other publicly accessible resources, allowing directory data to be queried without valid credentials.
Exploit preconditions
- Attack surface: The organization
loadOrSearchAPI endpoint - Required access: No authenticated account is required
- Trigger point: A request containing a valid or discoverable workspace identifier
- Why exploitation is possible: The endpoint returns organization directory data before verifying the caller's identity or authorization
Why this happens
The underlying issue is a missing authentication control on an internal API endpoint. The application permits requests to retrieve organization member and hierarchy information without first establishing an authenticated identity, which maps to CWE-306: Missing Authentication for Critical Function.
The insecure pattern is exposing a data-retrieval operation through a reachable API while relying on obscurity of workspace identifiers rather than enforcing authentication and authorization at the endpoint boundary.
Potential impact
- Attackers may enumerate member names and email addresses
- Organizational team structures could be disclosed
- Exposed contact information may support phishing or targeted social engineering
- Workspace membership could be used for reconnaissance and identity correlation
- Privacy, confidentiality, and regulatory compliance obligations could be affected
General mitigation guidance
Mitigation generally focuses on enforcing authentication and authorization consistently for every organization-directory operation.
Common defensive patterns include:
- Require a valid authenticated session or service identity before processing directory queries
- Apply workspace-level authorization checks after authentication
- Avoid treating shared links, public templates, or workspace identifiers as proof of authorization
- Return only the minimum directory data required for an authorized feature
- Use privacy-preserving defaults for member names, email addresses, and hierarchy data
- Apply rate limits, monitoring, and abuse controls to directory-search endpoints
- Run security tests that verify unauthenticated and cross-workspace requests are denied
How teams detect issues like this
Organizations can identify similar issues through:
- Static and semantic analysis that flags sensitive endpoints lacking authentication middleware
- Code review checks for routes that expose organization, user, or directory data
- API inventory reviews comparing internal endpoint classifications with enforced access policies
- Integration tests covering unauthenticated, cross-workspace, and insufficient-privilege requests
- Gateway or policy enforcement requiring authentication for organization-data API paths
- Monitoring for repeated directory queries, workspace-identifier enumeration, and unusual anonymous traffic
Neutral automated code-review and API-security tools may help identify missing access-control checks, but their findings should be validated against deployment-specific authorization rules.

