Skip to content
VulniPulse
Advisory severityHigh7.9Fortinet

High [CVE-2025-46773] Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability [CWE-89] vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.4, FortiAnalyzer 7.4.0 through 7.4.7, FortiAnalyzer 7.2 all versions, FortiAnalyzer Cloud 7.6.2 through 7.6.4, FortiAnalyzer Cloud 7.4.1 through 7.4.7, FortiAnalyzer Cloud 7.2.1 through 7.2.11 may allow a low privileged user to execute arbitrary commands via crafted requests

This high-severity Fortinet advisory covers CVE-2025-46773 affecting FortiAnalyzer Cloud.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2025-46773 Source published Source updated

VulniPulse record published

Affected products & platforms
FortinetFortiAnalyzer
Open source 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 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

An Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability [CWE-89] vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.4, FortiAnalyzer 7.4.0 through 7.4.7, FortiAnalyzer 7.2 all versions, FortiAnalyzer Cloud 7.6.2 through 7.6.4, FortiAnalyzer Cloud 7.4.1 through 7.4.7, FortiAnalyzer Cloud 7.2.1 through 7.2.11 may allow a low privileged user to execute arbitrary commands via crafted requests.

Affected versions
  • FortiAnalyzer Cloud 7.6.2 through 7.6.3
  • FortiAnalyzer Cloud 7.4.1 through 7.4.7
  • FortiAnalyzer Cloud 7.2.1 through 7.2.12
  • FortiAnalyzer 7.6.0 through 7.6.3
  • FortiAnalyzer 7.4.0 through 7.4.7
  • FortiAnalyzer 7.2.0 through 7.2.11

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

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

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

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · high-confidence parse· fetched 1 day 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.