CVE-2025-50538
[Flowise] Stored XSS via "View Messages" allows credential theft in FlowiseAI admin panel
Executive Summary
CVE-2025-50538 is a critical severity vulnerability affecting ai-code, binary-analysis, appsec, pii-secrets. It is classified as an undisclosed flaw. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.
Precogs AI Insight
"The underlying mechanism of this vulnerability involves within ### Summary, allowing the insecure processing of malicious payloads. A threat actor could leverage this oversight to intercept or modify sensitive data flows before they reach secure enclaves. The Precogs detection suite automatically flags these architectural defects to ensure strict authentication requirements are met."
What is this vulnerability?
CVE-2025-50538 is categorized as a critical Cross-Site Scripting (XSS) flaw. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.
Summary A stored Cross-Site Scripting (XSS) vulnerability in FlowiseAI allows a user to inject arbitrary JavaScript code via message input. When an ad.
This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.
Risk Assessment
| Metric | Value |
|---|---|
| CVSS Base Score | 9.5 (CRITICAL) |
| Vector String | N/A |
| Published | October 3, 2025 |
| Last Modified | October 3, 2025 |
| Related CWEs | N/A |
Impact on Systems
✅ Session Hijacking: Attackers can steal active user session tokens (cookies) to impersonate the victim.
✅ Phishing Execution: Malicious scripts can dynamically alter DOM content to present fraudulent login forms.
✅ Worm Propagation: Stored XSS can spread autonomously as users visit the infected page.
How to fix this issue?
Implement the following strategic mitigations immediately to eliminate the attack surface.
1. Output Encoding Implement strict context-aware output encoding (HTML, JavaScript, Attribute, CSS) before rendering user data.
2. Content Security Policy (CSP) Deploy a rigorous CSP header to restrict script execution exclusively to trusted domains.
3. Framework Defenses Utilize native UI framework protections (e.g., React DOM escaping) and avoid dangerouslySetInnerHTML.
Vulnerability Signature
// Example DOM-based XSS vulnerability
const user_input = new URLSearchParams(window.location.search).get('q');
// VULNERABLE: Direct insertion into innerHTML
document.getElementById('results').innerHTML = "Results for: " + user_input;
// EXPLOIT PAYLOAD: ?q=\<img src=x onerror=alert(document.cookie)\>
References and Sources
- NVD — CVE-2025-50538
- MITRE — CVE-2025-50538
- AI Code Security Vulnerabilities
- Binary Analysis Vulnerabilities
- Application Security Vulnerabilities
- PII and Secrets Exposure
Vulnerability Code Signature
Attack Data Flow
| Stage | Detail |
|---|---|
| Source | Network packet or file input |
| Vector | Data exceeds the allocated buffer bounds during a copy operation |
| Sink | strcpy(), memcpy(), or pointer arithmetic |
| Impact | Memory corruption, Remote Code Execution (RCE) |
Vulnerable Code Pattern
// ❌ VULNERABLE: Memory Corruption
void process_data(char *input) {
char buffer[128];
// Taint sink: copies without bounds checking
strcpy(buffer, input);
}
Secure Code Pattern
// ✅ SECURE: Bounded Memory Operations
void process_data(char *input) {
char buffer[128];
// Sanitized boundary check
strncpy(buffer, input, sizeof(buffer) - 1);
buffer[sizeof(buffer) - 1] = '\0';
}
How Precogs Detects This
Precogs Binary SAST engine explicitly uncovers memory boundary violations and unsafe memory management functions in compiled binaries.\n