# CVE-2025-12480: Gladinet Triofox Improper Access Control

> Attackers can access initial setup pages after installation, potentially bypassing security controls in Triofox file sharing software.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Yes, since 12 Nov 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Nov 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-26hx-622f-3855

## What is CVE-2025-12480?

CVE-2025-12480 is a critical missing authorization vulnerability in TrioFox, published on 10 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-12480?

It affects 1 product.


Products: Gladinet Triofox.

## How do I fix CVE-2025-12480?

No fix has been published for CVE-2025-12480 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 Dec 2025.

## Is CVE-2025-12480 being exploited?

Yes. Attackers have exploited CVE-2025-12480 in the wild since at least 12 Nov 2025.

Public exploit code:

- Triofox - Improper Access Control (nuclei): http/cves/2025/CVE-2025-12480.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12480 and fix it if it is affected.

What it is: CVE-2025-12480 is a critical missing authorization vulnerability in TrioFox, published on 10 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-12480 in the wild since at least 12 Nov 2025.

Affected product: TrioFox. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-12480/ (Markdown: https://insights.sbomify.com/CVE-2025-12480/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-12480
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-12480
- OSV: https://osv.dev/vulnerability/CVE-2025-12480

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-12480/
Summaries are generated and may contain mistakes; the official description above is the record.