Skip to main content
VulnerabilityPublished Updated

CVE-2024-54794: SpagoBI · Command Injection

Affects SpagoBISource CVE Database V5

0

Not known to be exploited · 12% EPSS · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 14:05 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Jan 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

Affected software

ProductAffectedFixed in
GitHubmariotesoro/SpagoBIpkg:github/mariotesoro/SpagoBIOther threatsAffected
  • =3.5.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately assess the deployment of SpagoBI 3.5.1 within your environment and identify instances where the script input feature is enabled.
  2. If possible, disable the script input feature temporarily until a vendor patch or official fix is released.
  3. Restrict network access to SpagoBI management interfaces to trusted administrators only, using network segmentation and firewall rules.
  4. Implement strict access controls and ensure that only necessary users have high privilege levels required to exploit this vulnerability.
  5. Monitor logs and system behavior for unusual command execution or suspicious activities indicative of exploitation attempts.
  6. Engage with the SpagoBI vendor or community to obtain patches or updates addressing this vulnerability as soon as they become available.
  7. Consider deploying application-layer firewalls or intrusion prevention systems capable of detecting and blocking command injection patterns related to CWE-77.
  8. Conduct security awareness training for administrators managing SpagoBI to recognize and respond to potential exploitation signs.
  9. Regularly back up critical data and verify recovery procedures to mitigate impact from potential attacks.

Description

The script input feature of SpagoBI 3.5.1 allows arbitrary code execution.

References

Community reviews

Loading reviews…