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

Back
New CVE Detected

CVE-2026-72536 – Unauthenticated Stripe Subscription Manipulation – Chaskiq (through commit 46dfdd1)

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-72536 is a missing authentication vulnerability (CWE-306) in Chaskiq, an open-source live chat, customer support, and marketing platform. The flaw resides in the stripeCreateIntent GraphQL mutation, which lacks any authentication or authorization checks, allowing unauthenticated remote attackers to manipulate any tenant’s Stripe subscription and billing state. The issue carries a CVSS v3.1 base score of 8.2 (High).

Technical details

  • Root cause: The stripeCreateIntent GraphQL mutation in Chaskiq does not enforce authentication or per-tenant authorization before processing requests.
  • Trigger conditions: An attacker sends a crafted GraphQL request invoking the stripeCreateIntent mutation against an exposed Chaskiq instance; no valid session, API key, or credentials are required.
  • Attack vector: Network-based (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N) — the mutation is reachable directly over the exposed GraphQL endpoint.
  • Impact: Because the mutation is tenant-scoped functionality that is missing access control, an attacker can create Stripe payment intents and alter subscription/billing data belonging to any tenant on the instance, resulting in low confidentiality impact, high integrity impact, and low availability impact.

Affected software

  • Chaskiq, all versions through commit 46dfdd1 (i.e., versions "0 through 46dfdd1" as recorded in the official CVE entry).

Severity

  • CVSS v3.1 Base Score: 8.2 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L

Mitigation and recommended actions

  • Immediate: No vendor-published patched release or official security advisory is currently available beyond the CVE record itself. Organizations running Chaskiq should track the upstream project repository for a fix that adds authentication/authorization checks to the stripeCreateIntent GraphQL mutation, and update to a patched commit/release as soon as one is published.
  • If no patch is available:
    • Restrict or disable public access to the Chaskiq GraphQL endpoint (e.g., place it behind authentication at the reverse proxy/API gateway layer, or restrict to trusted networks/VPN).
    • Apply GraphQL query allow-listing or disable introspection/unused mutations, including stripeCreateIntent, if not actively required from unauthenticated contexts.
    • Monitor Stripe account activity and webhook logs for unexpected payment intent creation or subscription changes tied to Chaskiq tenants.
    • Rotate and tightly scope Stripe API keys used by the Chaskiq integration, and enable Stripe-side alerting for anomalous intent creation.
    • Consider isolating the Chaskiq instance behind a WAF or authentication proxy until an upstream fix is confirmed and deployed.

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