Skip to content
VulniPulse
Critical9.8Fortinet

Critical [CVE-2025-25256] improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerability [CWE-78] vulnerability in Fortinet FortiSIEM 7.3.0 through 7.3.1, FortiSIEM 7.2.0 through 7.2.5, FortiSIEM 7.1.0 through 7.1.7, FortiSIEM 7.0.0 through 7.0.3, FortiSIEM 6.7.0 through 6.7.9, FortiSIEM 6.6 all versions, FortiSIEM 6.5 all versions, FortiSIEM 6.4 all versions, FortiSIEM 6.3 all versions, FortiSIEM 6.2 all versions, FortiSIEM 6.1 all versions, FortiSIEM 5.4 all versions, FortiSIEM 5.3 all versions, FortiSIEM 5.2 all versions, FortiSIEM 5.1 all versions, FortiSIEM 5.0 all versions, FortiSIEM 4.10 all versions, FortiSIEM 4.9 all versions, FortiSIEM 4.7 all versions allows an unauthenticated attacker to execute unauthorized code or commands via crafted CLI requests

This critical-severity Fortinet advisory covers CVE-2025-25256 affecting FortiSIEM.

CVE-2025-25256 Published Aug 12, 2025Updated by vendor Aug 18, 2026
Affected products & platforms
FortinetFortiSIEM
Open vendor advisory

Android app · Google Play

Monitor future Fortinet CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

An improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerability [CWE-78] vulnerability in Fortinet FortiSIEM 7.3.0 through 7.3.1, FortiSIEM 7.2.0 through 7.2.5, FortiSIEM 7.1.0 through 7.1.7, FortiSIEM 7.0.0 through 7.0.3, FortiSIEM 6.7.0 through 6.7.9, FortiSIEM 6.6 all versions, FortiSIEM 6.5 all versions, FortiSIEM 6.4 all versions, FortiSIEM 6.3 all versions, FortiSIEM 6.2 all versions, FortiSIEM 6.1 all versions, FortiSIEM 5.4 all versions, FortiSIEM 5.3 all versions, FortiSIEM 5.2 all versions, FortiSIEM 5.1 all versions, FortiSIEM 5.0 all versions, FortiSIEM 4.10 all versions, FortiSIEM 4.9 all versions, FortiSIEM 4.7 all versions allows an unauthenticated attacker to execute unauthorized code or commands via crafted CLI requests.

Affected versions
  • FortiSIEM 7.3: 7.3.0 through 7.3.1
  • FortiSIEM 7.2: 7.2.0 through 7.2.5
  • FortiSIEM 7.1: 7.1.0 through 7.1.7
  • FortiSIEM 7.0: 7.0.0 through 7.0.3
  • FortiSIEM 6.7: 6.7.0 through 6.7.9
  • FortiSIEM 6.6: 6.6 all versions
  • FortiSIEM 6.5: 6.5 all versions
  • FortiSIEM 6.4: 6.4 all versions
  • FortiSIEM 6.3: 6.3 all versions
  • FortiSIEM 6.2: 6.2 all versions
  • FortiSIEM 6.1: 6.1 all versions
  • FortiSIEM 5.4: 5.4 all versions
  • FortiSIEM 5.3: 5.3 all versions
  • FortiSIEM 5.2: 5.2 all versions
  • FortiSIEM 5.1: 5.1 all versions
  • FortiSIEM 5.0: 5.0 all versions
  • FortiSIEM 4.10: 4.10 all versions
  • FortiSIEM 4.9: 4.9 all versions
  • FortiSIEM 4.7: 4.7 all versions

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Fixed versions
  • FortiSIEM 7.3: 7.3.2
  • FortiSIEM 7.2: 7.2.6
  • FortiSIEM 7.1: 7.1.8
  • FortiSIEM 7.0: 7.0.4
  • FortiSIEM 6.7: 6.7.10
  • FortiSIEM 6.6: migrate to a fixed release
  • FortiSIEM 6.5: migrate to a fixed release
  • FortiSIEM 6.4: migrate to a fixed release
  • FortiSIEM 6.3: migrate to a fixed release
  • FortiSIEM 6.2: migrate to a fixed release
  • FortiSIEM 6.1: migrate to a fixed release
  • FortiSIEM 5.4: migrate to a fixed release
  • FortiSIEM 5.3: migrate to a fixed release
  • FortiSIEM 5.2: migrate to a fixed release
  • FortiSIEM 5.1: migrate to a fixed release
  • FortiSIEM 5.0: migrate to a fixed release
  • FortiSIEM 4.10: migrate to a fixed release
  • FortiSIEM 4.9: migrate to a fixed release
  • FortiSIEM 4.7: migrate to a fixed release

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Upgrade per the Affected/Solution table: FortiSIEM 7.3: 7.3.2; FortiSIEM 7.2: 7.2.6; FortiSIEM 7.1: 7.1.8; FortiSIEM 7.0: 7.0.4; FortiSIEM 6.7: 6.7.10; ….
Temporary workarounds
  • Limit access to the phMonitor port (7900)

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.