CVE-2026-70476
Received Received - Intake

Unauthorized Stripe Subscription Modification in Flowise

Publication date: 2026-08-04

Last updated on: 2026-08-04

Assigner: GitHub, Inc.

Description
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, several organization billing endpoints in packages/server/src/enterprise/routes/organization.route.ts and packages/server/src/enterprise/controllers/organization.controller.ts accept attacker-controlled Stripe subscriptionId values without verifying that the identifier belongs to the authenticated user's organization. An authenticated attacker can perform unauthorized Stripe subscription operations on other tenants, including changing subscription plans or modifying seat quantities, resulting in financial impact and service disruption. This issue is fixed in 3.1.3.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-04
Last Modified
2026-08-04
Generated
2026-08-05
AI Q&A
2026-08-04
EPSS Evaluated
N/A
NVD
CVE-2026-70476
EUVD
EUVD-2026-52872

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
flowiseai flowise to 3.1.3 (exc)
flowiseai flowise 3.1.3
flowise flowise to 3.1.3 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a Broken Access Control issue in Flowise software versions 3.1.2 and earlier. It allows authenticated attackers to manipulate Stripe subscription details of other organizations by exploiting improper validation of subscription identifiers. The server accepts user-supplied subscription IDs without verifying ownership, enabling unauthorized changes to subscription plans or seat quantities.

Detection Guidance

To detect this vulnerability, check if your Flowise instance is running a version prior to 3.1.3. Inspect logs for unauthorized Stripe subscription modifications or access attempts to endpoints like /update-additional-seats or /update-subscription-plan. Look for mismatched Stripe IDs in requests compared to session data.

Impact Analysis

An attacker could downgrade your subscription plan, reduce seat counts, or upgrade to higher-priced plans. This could lead to financial loss, service disruption, or unauthorized access to resources tied to your organization's billing.

Compliance Impact

This vulnerability could lead to unauthorized billing changes, potentially violating financial compliance requirements in GDPR and HIPAA. Unauthorized modifications to subscription plans or seat quantities may result in improper data processing or billing practices, which could conflict with regulatory obligations for data integrity and security.

Mitigation Strategies

Upgrade Flowise to version 3.1.3 or later immediately. Review logs for suspicious activity related to Stripe subscription changes. Ensure the new validation checks for Stripe ID ownership are enforced in your environment.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-70476. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart