Secuno
ENNL
Book demo

CVE-2025-29192

Flowiseai Flowise cross-site scripting (XSS)

8.2 HIGHPublic exploitEPSS 0.41%
  1. Published6 Oct 2025

Description

Flowise before 3.0.5 allows XSS via a FORM element and an INPUT element when an admin views the chat log.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionRequired
ScopeChanged
ConfidentialityHigh
IntegrityLow
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N

Affected products

Flowiseai Flowise< 3.0.5

Remediation

Fixed in
Flowiseai Flowise≥ 3.0.5

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-928838.7
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.1 before…
CVE-2026-938868.3
IBM i 7.3, 7.4, 7.5, and 7.6 could allow a remote authenticated attacker to execute…
CVE-2026-1096338.1
Frappe ERPNext before 15.119.1 and 16.x before 16.32.0 contains a stored cross-site…
CVE-2025-714328.1
Frappe ERPNext before 14.92.1 and 15.x before 15.83.0 contains a reflected cross-site…
CVE-2026-1095588.7
EdgeEver 1.6.0 through 1.112.0 contains a stored cross-site scripting vulnerability in…
CVE-2026-1095578.7
EdgeEver through 1.112.0 contains a stored cross-site scripting vulnerability in…

Frequently asked

Is CVE-2025-29192 being actively exploited?

CVE-2025-29192 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.41%.

How severe is CVE-2025-29192?

CVE-2025-29192 has a CVSS 3.1 base score of 8.2, rated high. EPSS estimates a 0.41% probability of exploitation.

Which products are affected by CVE-2025-29192?

Affected products include Flowiseai Flowise.

How do I fix CVE-2025-29192?

Upgrade affected software to a fixed version, for example Flowiseai Flowise 3.0.5 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-29192 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.