CVE-2025-12480
Published: November 12, 2025
Official Description
Gladinet Triofox contains an improper access control vulnerability that allows access to initial setup pages even after setup is complete.
CISA KEV Advisory
Gladinet Triofox Improper Access Control Vulnerability
Gladinet Triofox contains an improper access control vulnerability that allows access to initial setup pages even after setup is complete.
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Risk Analysis
Gladinet Triofox suffers from an improper access control vulnerability, allowing access to initial setup pages even after the setup process is complete. With an EPSS score of 0.73223 and confirmed exploitation by CISA (is_in_kev: true), this is a high-priority vulnerability that is actively being exploited.
This vulnerability is actively exploited in the wild, indicating a severe and immediate risk. Its inclusion in CISA's KEV confirms its active use by attackers.
Administrators of Gladinet Triofox should apply the latest security patches to correct the improper access control. Ensure that all setup and configuration pages are properly secured post-installation.
Technical Analysis
CVE-2025-12480 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2025-12480 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Exploit & PoC Resources
All References (2)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2025-12480 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1