dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 Dec 2025.
TriofoxApplication · Gladinet

CVE-2025-12480

CRITICAL · 9.1 CVSS v3.1 Published 2025-11-10
Fix available
A fix is available. Upgrade to 16.7.10368.56560 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Triofox versions prior to 16.7.10368.56560 contain an improper access control vulnerability that allows unauthenticated access to initial setup pages even after the software has been fully configured and deployed. This enables attackers to potentially access or manipulate setup functions that should be restricted post-installation.

MitigationUpgrade Triofox to version 16.7.10368.56560 or later to remediate the access control flaw. As a compensating control, restrict network access to setup/admin URLs at the perimeter until patching is feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TriofoxApplication
Affected:< 16.7.10368.56560

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Triofox installed version
    Access the Triofox admin interface or About page (typically via Help > About or /admin/settings in the web UI) and note the exact version number displayed
    Affected if The displayed version is less than 16.7.10368.56560
  2. Identify setup page URL patterns
    Locate the initial setup pages - these are typically accessed via URLs containing /setup, /install, /initial, or /wizard in the application root or admin path
    Affected if Setup page URLs are discoverable and follow common patterns such as /setup, /install.aspx, or similar
  3. Test setup page accessibility without authentication
    Open a private/incognito browser window and navigate to the known setup page URLs without providing any credentials. Observe whether the pages load and are interactive
    Affected if Setup pages render and accept input without requiring authentication or returning an access denied error
  4. Verify setup completion status
    Check if the system indicates setup has already been completed (look for indicators like 'Setup Complete' messages, configured admin accounts, or populated configuration tables in the database)
    Affected if Setup appears completed but the setup pages are still accessible

The environment is affected if Triofox version is below 16.7.10368.56560 AND the initial setup pages remain accessible without authentication after the setup process has been completed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 16.7.10368.56560 or later
Fixed in 16.7.10368.56560
Interim mitigation

Upgrade Triofox to version 16.7.10368.56560 or later to remediate the access control flaw. As a compensating control, restrict network access to setup/admin URLs at the perimeter until patching is feasible.

Recommended fix High confidence

16.7.10368.56560 or later

  1. Back up the current Triofox installation and configuration data before proceeding with the upgrade
  2. Download the fixed version 16.7.10368.56560 or later from the official Triofox download portal (access.triofox.com or www.triofox.com)
  3. Install or apply the upgrade following the standard Triofox upgrade procedure documented in the product manual
  4. After upgrade completion, verify that initial setup pages are no longer accessible without proper authentication
  5. Confirm the upgrade was successful by checking the Triofox version information in the admin console

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Triofox Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12480 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12480 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data