Skip to content
Fencer Intel
critical 9.1

CVE-2025-12480 kev in the critical feed json

Triofox versions prior to 16.7.10368.56560, are vulnerable to an Improper Access Control flaw that allows access to initial setup pages eve…

published last yr. modified 23d ago also EUVD-2025-44062

cvss
9.1
version 3.1, CNA
cisa kev
Exploited
added 2025-11-12
epss
95.7%
EPSS 95.7% chance of exploitation in 30 days, percentile 99.8%
public exploits
0
none known

Summary

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.

Patch / fix

cisa required action Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

  • TrioFox TrioFox 16.7.10368.56560

Is CVE-2025-12480 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. CISA SSVC: exploitation active
  3. Added to CISA KEV
  4. CISA patch deadline

Known exploited

Added
last yr.
Patch by
2025-12-03 (11mo ago)
Ransomware
Not known
Required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vendor, product
Gladinet, Triofox
CISA name
Gladinet Triofox Improper Access Control Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

95.75% chance of exploitation in the next 30 days, higher than 99.8% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • cloud.google.com https://cloud.google.com/blog/topics/threat-intelligence/triofox-vulnerability-cve-2025-12480 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

  • TrioFox TrioFox

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.