/

CVE-2026-72536

Severity:

HIGH RISK

(8.6)

Missing Authentication (CWE-306) in Chaskiq Stripe API

CVE-2026-72536

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Unauthorized payment and subscription manipulation

Severity:

HIGH RISK

(8.6)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Chaskiq exposes the stripeCreateIntent GraphQL mutation without sufficient authentication or authorization checks. An unauthenticated remote attacker may create Stripe payment intents and manipulate subscription billing for tenants through the exposed API.

Affected context

The vulnerability occurs in Chaskiq deployments that expose the GraphQL API containing the stripeCreateIntent mutation and do not enforce authentication and tenant-level authorization before processing requests. Risk is greatest when the endpoint is reachable over a network and payment operations are accepted without verifying the caller's identity, tenant scope, or privileges.

Exploit preconditions

  • Attack surface: Network-accessible Chaskiq GraphQL API
  • Required access: No credentials or authenticated session
  • Trigger point: Invocation of the stripeCreateIntent mutation
  • Why exploitation is possible: The mutation can process payment-intent creation without enforcing authentication and authorization checks

Why this happens

The underlying flaw is a missing authentication control on a sensitive GraphQL mutation. The application treats requests to stripeCreateIntent as actionable without first establishing the caller's identity and verifying that the caller is authorized to operate on the selected tenant. This behavior maps to CWE-306: Missing Authentication for Critical Function, because a security-sensitive function is available without the required authentication boundary.

Potential impact

  • An attacker may create unauthorized Stripe payment intents.
  • Tenant subscription billing could be altered without permission.
  • Organizations may incur fraudulent charges or payment-processing costs.
  • Billing records and subscription state could become inconsistent.
  • The issue could cause financial, operational, and reputational harm.

General mitigation guidance

Mitigation generally focuses on placing strong identity and authorization controls at the GraphQL resolver and service boundaries.

Common defensive patterns include:

  • Requiring authentication before processing payment or subscription mutations.
  • Enforcing tenant-scoped authorization for every billing operation.
  • Deriving tenant identity from the authenticated session rather than caller-controlled values.
  • Applying least privilege to payment-related service accounts and API credentials.
  • Validating mutation inputs and enforcing server-side business rules.
  • Using secure-by-default GraphQL policies that deny sensitive operations unless explicitly permitted.
  • Recording and reviewing payment-intent creation events for anomalous activity.

How teams detect issues like this

Organizations commonly detect missing authentication and authorization through:

  • Static analysis and policy checks for sensitive resolvers without authentication middleware.
  • Code review of GraphQL mutations that create, modify, or cancel payment resources.
  • Tests that invoke sensitive operations without credentials and verify denial.
  • Tests that use an authenticated principal from one tenant against another tenant's resources.
  • API gateway and GraphQL policy enforcement requiring identity and tenant context.
  • Monitoring for anonymous calls, unusual payment-intent creation rates, and cross-tenant access attempts.

Automated code review tools may help identify resolvers that bypass shared authentication or authorization controls.

Sources

SourceLink
github.comgithub.com/chaskiq/chaskiq

Frequently asked

questions

Yes, when the affected GraphQL endpoint is reachable by an attacker and the mutation remains exposed without authentication. The described issue does not require a local foothold.

No. The vulnerability is characterized by missing authentication, so an unauthenticated caller may be able to invoke the payment mutation.

Require authentication and enforce tenant-scoped authorization before any payment intent or subscription operation is processed. Authorization should be checked server-side and should not rely on client-supplied tenant identifiers.

Classify payment mutations as privileged operations, apply deny-by-default GraphQL policies, add unauthenticated and cross-tenant authorization tests, and monitor billing APIs for anomalous activity.

Find out what's already
exploitable in your codebase.