Skip to main content
VulnerabilityPublished

CVE-2025-65790: FuguHub · Cross-site Scripting

Source CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2025-65790, European organizations should implement the following specific measures: 1) Immediately restrict or disable the upload and serving of SVG files through the /fs/ file manager interface until a patch is available. 2) Employ strict content security policies (CSP) that disallow inline scripts and restrict script sources to trusted domains, reducing the risk of script execution from SVG files. 3) Use web application firewalls (WAFs) to detect and block malicious payloads targeting the SVG handling functionality. 4) Educate users about the risks of opening SVG files from untrusted sources and implement user awareness campaigns to reduce successful phishing attempts. 5) Monitor logs and network traffic for suspicious activity related to SVG file access or unusual script execution patterns. 6) Engage with FuguHub vendors or community to obtain patches or updates as soon as they become available and prioritize their deployment. 7) Consider implementing file type validation and sanitization at the gateway or proxy level to prevent malicious SVG content from reaching end users. 8) Review and tighten permissions on the file manager interface to limit exposure to only necessary users. These targeted actions go beyond generic advice and focus on the specific attack vector and environment.

Description

A reflected cross-site scripting (XSS) vulnerability exists in FuguHub 8.1 when serving SVG files through the /fs/ file manager interface. FuguHub does not sanitize or restrict script execution inside SVG content. When a victim opens a crafted SVG containing an inline <script> element, the browser executes the attacker-controlled JavaScript.

References

Community reviews

Loading reviews…