Threats / Gladinet / CVE-2025-12480
CVE-2025-12480
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Gladinet Triofox vulnerability
Gladinet Triofox contains an improper access control vulnerability allowing access to initial setup pages after setup completion, enabling unauthorized configuration changes.
Verdict
Today item — known-exploited.
An unauthenticated or low-privileged attacker can bypass access controls to reach setup interfaces in Triofox, potentially reconfiguring the application or extracting sensitive information exposed during initial setup flows.
CISA KEV Yes · 2025-11-125EPSS 0.90532 (verify live)6CVSS 9.13CISA SSVC Exploitation: active · Automatable: yes · Impact: total4Exploit Public PoC / detection · nuclei template13
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
162 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-11-12).
Probability (EPSS)
EPSS 0.90532 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) · Affected: Gladinet, Triofox. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-284 Improper Access Control — weakness family: Authorization / access control.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 2 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify that setup pages remain accessible after initial configuration is complete due to missing access control checks.
Business
Attackers gain unauthorized entry to administrative functions, creating risk of data exposure and system reconfiguration without detection.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I access setup wizards to view or modify configuration parameters, credentials, or integration settings stored in the application.
Business
Sensitive credentials and system configurations become compromised, enabling lateral movement or privilege escalation within the deployment.
3
Lateral reach — past segmentation narrative 3
Attacker
I reset or reconfigure Triofox settings to redirect data flows, disable security controls, or establish persistence mechanisms.
Business
Operational integrity is compromised as attackers alter system behavior to facilitate data theft, service disruption, or further compromise.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by MandiantCNA
Credited with finding itStallone D’Souza, Mandiantfinder