CVE-2025-65790

6.1 MEDIUM

📋 TL;DR

A reflected cross-site scripting vulnerability in FuguHub 8.1 allows attackers to execute arbitrary JavaScript in victims' browsers by tricking them into opening malicious SVG files. This affects all users of FuguHub 8.1 who access the /fs/ file manager interface. Attackers can steal session cookies, redirect users, or perform actions on their behalf.

💻 Affected Systems

Products:
  • FuguHub
Versions: 8.1
Operating Systems: All platforms running FuguHub
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability exists in default configuration when SVG files are served through the /fs/ interface.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete account takeover, data theft, and privilege escalation if attacker steals admin session cookies or performs malicious actions as authenticated users.

🟠

Likely Case

Session hijacking, credential theft, and unauthorized actions performed in victims' browser context.

🟢

If Mitigated

Limited impact if proper content security policies are enforced and users don't open untrusted SVG files.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploitation requires victim interaction (opening malicious SVG file) but is technically simple with public proof-of-concept available.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://fuguhub.com/

Restart Required: No

Instructions:

No official patch available. Monitor vendor website for security updates. Consider workarounds or alternative solutions.

🔧 Temporary Workarounds

Disable SVG file serving

all

Configure web server or application to block SVG file types from being served through the /fs/ interface.

# Apache: Add to .htaccess or virtual host config
<FilesMatch "\.svg$">
    Deny from all
</FilesMatch>
# Nginx: Add to server block
location ~*\.svg$ {
    deny all;
}

Implement Content Security Policy

all

Add CSP headers to prevent inline script execution in SVG files.

# Add to web server configuration or application headers
Content-Security-Policy: script-src 'self'; object-src 'none';

🧯 If You Can't Patch

  • Implement WAF rules to block SVG files containing script tags or JavaScript content.
  • Restrict access to /fs/ interface to trusted users only using authentication and IP whitelisting.

🔍 How to Verify

Check if Vulnerable:

Upload an SVG file containing <script>alert('XSS')</script> to /fs/ interface and attempt to access it. If alert triggers, system is vulnerable.

Check Version:

Check FuguHub admin interface or configuration files for version information. Typically found in admin panel or /version endpoint.

Verify Fix Applied:

Test with same malicious SVG file after implementing workarounds. Alert should not trigger and file should be blocked or sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SVG file uploads to /fs/ endpoint
  • Multiple failed SVG file access attempts
  • Requests to /fs/ with SVG files containing script patterns

Network Indicators:

  • HTTP requests for SVG files with suspicious parameters or content
  • Traffic patterns showing SVG file uploads followed by immediate access

SIEM Query:

source="web_logs" AND uri_path="/fs/*.svg" AND (http_user_agent CONTAINS "script" OR http_referer CONTAINS "svg")

🔗 References

📤 Share & Export