CVE-2025-63391
📋 TL;DR
An authentication bypass vulnerability in Open-WebUI's /api/config endpoint allows unauthenticated remote attackers to access sensitive system configuration data. This affects all Open-WebUI deployments running version 0.6.32 or earlier. Attackers can retrieve configuration details that could facilitate further attacks.
💻 Affected Systems
- Open-WebUI
📦 What is this software?
Open Webui by Openwebui
⚠️ Risk & Real-World Impact
Worst Case
Attackers obtain full system configuration including API keys, database credentials, and deployment details, enabling complete system compromise, data exfiltration, or lateral movement.
Likely Case
Attackers harvest sensitive configuration data like API keys and internal endpoints, which can be used for credential theft, reconnaissance, or targeted follow-up attacks.
If Mitigated
With proper authentication controls, only authorized administrators can access configuration data, limiting exposure to legitimate users.
🎯 Exploit Status
Simple HTTP GET request to /api/config endpoint without authentication.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: > 0.6.32
Vendor Advisory: https://github.com/open-webui/open-webui/issues
Restart Required: Yes
Instructions:
1. Update Open-WebUI to version >0.6.32. 2. Restart the Open-WebUI service. 3. Verify the /api/config endpoint now requires authentication.
🔧 Temporary Workarounds
Network Access Control
linuxRestrict access to the /api/config endpoint using firewall rules or web server configuration.
iptables -A INPUT -p tcp --dport <webui-port> -m string --string '/api/config' --algo bm -j DROP
Reverse Proxy Authentication
allPlace Open-WebUI behind a reverse proxy that enforces authentication for the /api/config endpoint.
🧯 If You Can't Patch
- Deploy network segmentation to isolate Open-WebUI from untrusted networks.
- Implement web application firewall (WAF) rules to block unauthenticated requests to /api/config.
🔍 How to Verify
Check if Vulnerable:
Send HTTP GET request to http://<target>:<port>/api/config without authentication. If it returns configuration data, system is vulnerable.Check Version:
Check Open-WebUI version in web interface or configuration files.Verify Fix Applied:
After patching, same unauthenticated request should return 401/403 error or no data.📡 Detection & Monitoring
Log Indicators:
- HTTP 200 responses to GET /api/config from unauthenticated IPs
- Unusual access patterns to configuration endpoint
Network Indicators:
- Unauthenticated HTTP GET requests to /api/config endpoint
- Traffic spikes to configuration endpoint
SIEM Query:
source="webui.log" AND (uri="/api/config" AND status=200 AND NOT user_authenticated=true)