Summary
Chaskiq contains a missing authentication and authorization check in the stripeCustomerPortal GraphQL mutation. An unauthenticated remote attacker may create Stripe Billing Portal sessions for arbitrary tenants and access or manage their subscription information when the vulnerable mutation is exposed.
Affected context
The issue may affect Chaskiq deployments that expose the vulnerable GraphQL mutation and permit requests to reach the Stripe customer portal integration. Risk is present when the mutation can be invoked without an authenticated user context and does not verify that the requested tenant is authorized for the caller.
Exploit preconditions
- Attack surface: Internet-accessible or otherwise reachable Chaskiq GraphQL API
- Required access: No valid credentials may be required when the vulnerable mutation is exposed
- Trigger point: Invocation of the
stripeCustomerPortalmutation - Tenant condition: The request can reference a tenant or Stripe account without an effective ownership check
- Why exploitation is possible: The mutation creates a billing portal session before enforcing authentication and tenant-level authorization
Why this happens
The underlying flaw is an authentication and authorization omission in a sensitive GraphQL resolver. The resolver performs a billing-related action without first establishing the caller's identity or confirming that the caller is permitted to act for the selected tenant. This behavior maps to CWE-306: Missing Authentication for Critical Function, with a related cross-tenant authorization failure because tenant ownership is not enforced.
Potential impact
- An unauthenticated attacker may obtain billing portal access for another tenant
- Attackers could view subscription and billing-related information
- Attackers may modify subscription settings or other options available through the portal
- Tenant confidentiality and isolation could be weakened
- Organizations may face unauthorized billing changes or service disruption
General mitigation guidance
Mitigation generally focuses on enforcing identity and tenant authorization before any billing session is created.
Common defensive patterns include:
- Require authentication for all sensitive GraphQL mutations
- Verify that the authenticated principal is authorized for the requested tenant
- Derive tenant identity from trusted server-side session context rather than client-supplied values
- Apply deny-by-default authorization policies to billing and account-management operations
- Use short-lived, narrowly scoped portal sessions
- Avoid exposing internal tenant or Stripe account identifiers as sufficient authorization
- Run authorization and tenant-isolation tests for every sensitive resolver
How teams detect issues like this
Organizations can look for this weakness through:
- Static analysis and code review checks for sensitive resolvers lacking authentication guards
- Review of GraphQL mutations that create tokens, sessions, payment links, or account-management capabilities
- Tests that invoke billing operations without credentials and with users from unrelated tenants
- API gateway or GraphQL policy enforcement requiring authenticated principals for sensitive operations
- Audit-log monitoring for portal-session creation without a corresponding authenticated user and tenant authorization decision
Automated security review tools may help identify resolver paths that access billing functionality without consistent identity and authorization checks.

