CVE-2024-25831: F-logic DataCube3 · Cross-site Scripting
Source CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% 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:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Feb 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-2024-25831, organizations should implement strict input validation and output encoding on all user-supplied data within the web management interface to prevent script injection. Employing a robust Content Security Policy (CSP) can help restrict the execution of unauthorized scripts. Access to the management interface should be tightly controlled using network segmentation, VPNs, or IP whitelisting to limit exposure. Multi-factor authentication (MFA) should be enforced to reduce the risk of compromised credentials. Administrators should be trained to recognize phishing attempts that could lead to malicious link clicks. Regular monitoring and logging of management interface activities can help detect suspicious behavior early. Since no official patches are currently available, consider applying web application firewalls (WAF) with custom rules to detect and block XSS payloads targeting this interface. Stay alert for vendor updates or patches and apply them promptly once released.
Description
F-logic DataCube3 Version 1.0 is affected by a reflected cross-site scripting (XSS) vulnerability due to improper input sanitization. An authenticated, remote attacker can execute arbitrary JavaScript code in the web management interface.