CVE-2025-53680: Command injection in CLI
An improper neutralization of special elements used in an OS command ("OS Command Injection") vulnerability [CWE-78] in FortiAP, FortiAP-U & FortiAP-W2 CLI may allow an authenticated privileged attacker to execute unauthorized code or commands via crafted CLI requests.
Other sources
An improper neutralization of special elements used in an OS command ("OS Command Injection") vulnerability [CWE-78] vulnerability in Fortinet FortiAP 7.6.0 through 7.6.2, FortiAP 7.4.0 through 7.4.5, FortiAP 7.2 all versions, FortiAP 7.0 all versions, FortiAP 6.4 all versions, FortiAP-U 7.0.0 through 7.0.5, FortiAP-U 6.2 all versions, FortiAP-W2 7.4.0 through 7.4.4, FortiAP-W2 7.2 all versions, FortiAP-W2 7.0 all versions allows an authenticated privileged attacker to execute unauthorized code or commands via crafted CLI requests.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Fortinet FortiAPto a version that resolves this vulnerability.Fixed in 7.4.6 - Upgrade
Upgrade
Fortinet FortiAPto a version that resolves this vulnerability.Fixed in 7.6.3 - Upgrade
Upgrade
Fortinet FortiAP-Uto a version that resolves this vulnerability.Fixed in 7.0.6 - Upgrade
Upgrade
Fortinet FortiAP-W2to a version that resolves this vulnerability.Fixed in 7.4.5
Event History
Frequently Asked Questions
What is the severity of CVE-2025-53680?
CVE-2025-53680 is considered a high severity vulnerability due to the potential for unauthorized code execution.
How do I fix CVE-2025-53680?
To fix CVE-2025-53680, update your FortiAP devices to the latest versions specified in the vendor's advisory.
What products are affected by CVE-2025-53680?
CVE-2025-53680 affects various FortiAP models including FortiAP, FortiAP-U, and FortiAP-W2 across specific software versions.
Can CVE-2025-53680 be exploited remotely?
CVE-2025-53680 requires an authenticated privileged attacker, making it less likely to be exploited remotely.
Is there a workaround for CVE-2025-53680?
There is currently no known workaround for CVE-2025-53680, and applying the appropriate updates is recommended.