Unauthenticated LFI in Gladinet CentreStack and Triofox via Hardcoded AES Cryptographic Values
CVE-2025-14611 affects Gladinet CentreStack and Triofox versions prior to 16.12.10420.56791. The vulnerability is caused by hardcoded values in the products’ AES cryptosystem implementation, described in the supporting content as fixed cryptographic keys and initialization vectors embedded across vulnerable installations. Because these values are not unique per deployment, attackers can recover or rely on the known cryptographic material to decrypt or forge protected access tickets. In exposed deployments, a specially crafted unauthenticated request to affected endpoints can bypass intended protections and trigger arbitrary local file inclusion (LFI), including retrieval of sensitive files such as web.config. The weakness degrades the security of publicly exposed endpoints and can be chained with other Gladinet vulnerabilities for broader compromise.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a full proof-of-concept exploit for CVE-2025-14611, a critical vulnerability in Gladinet CentreStack and Triofox (all versions prior to 16.12.10420.56791) on Windows. The vulnerability is due to hardcoded AES-256 keys in the application binary, allowing attackers to forge access tickets and read arbitrary files from the server via the /storage/filesvr.dn HTTP endpoint. The exploit consists of a single Python script (exploit.py) that can both generate (encrypt) and analyze (decrypt) access tickets. The script constructs a malicious ticket by encrypting the target file path (default: web.config), empty username and password (to trigger authentication bypass), and a far-future timestamp (to bypass expiration checks). The resulting ticket is embedded in a URL, which can be used with curl or a browser to retrieve the file from a vulnerable server. The README.md provides extensive technical details, including reverse engineering findings, cryptographic key extraction, and real-world attack scenarios. The exploit enables attackers to obtain sensitive files (such as web.config with machine keys), which can be further leveraged for remote code execution via ViewState deserialization attacks. The repository is operational and provides all necessary components for successful exploitation.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
33 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical insecure cryptography vulnerability in Gladinet CentreStack and TrioFox involving hardcoded AES cryptographic values, which can enable arbitrary local file inclusion and be chained toward full system compromise.
An unauthenticated local file inclusion (LFI) vulnerability in Gladinet CentreStack and Triofox, caused by hardcoded values in the AES cryptoscheme, allows attackers to include arbitrary local files via specially crafted requests. This affects publicly exposed endpoints and is actively exploited.
A vulnerability in CentreStack and Triofox where hardcoded cryptographic keys allow attackers to decrypt and forge access tickets, enabling persistent unauthorized access.
A critical vulnerability in Gladinet CentreStack and Triofox platforms due to hardcoded cryptographic keys, allowing attackers to decrypt data, bypass integrity checks, and potentially achieve remote code execution when chained with other flaws.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.