CVE-2025-14771
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 · uneditedFiles or directories accessible to external parties vulnerability in ABB T-MAC Plus. This issue affects T-MAC Plus: 4.0-24.
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 confidenceAn information disclosure vulnerability in ABB T-MAC Plus allows unauthorized external access to files or directories. This likely represents a path traversal, directory listing, or insecure file serving configuration that exposes sensitive system files to unauthenticated network attackers. The CRITICAL 9.9 CVSS indicates network-exploitable exposure with no authentication required.
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= 4.0-24CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed T-MAC Plus versionLocate the T-MAC Plus installation directory and check the version information file, or use the application's About/Version dialog if accessible through the client interface. Common locations include the program installation folder or registry entries for installed software.Affected if The installed version is 4.0-24 or any version prior to the patched release (version number less than 4.0-24 in the 4.0.x series).
-
Determine if the T-MAC Plus web interface is enabledCheck the T-MAC Plus configuration files or service settings for web server or HTTP service status. Look for configuration parameters that enable the web-based management interface or API endpoints.Affected if The web interface or HTTP-based service is enabled and running on the affected system.
-
Verify network exposure of the T-MAC Plus serviceReview network binding configurations and firewall rules to determine which network interfaces the T-MAC Plus service listens on. Use netstat or equivalent to identify listening ports associated with T-MAC Plus.Affected if The T-MAC Plus service is bound to a non-local interface or is accessible from networks other than trusted management subnets.
-
Inspect access control configurationExamine T-MAC Plus configuration files for authentication settings, IP allowlists, or access control lists that restrict access to the management interface. Check for any anonymous or unauthenticated access permissions.Affected if No IP-based access restrictions are configured, or anonymous access to file/directory features is permitted.
You are affected if T-MAC Plus version 4.0-24 is installed and the web or network interface is accessible to untrusted external parties without proper access controls.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataRestrict web server configuration to prevent unauthorized file/directory access, implement proper authentication and authorization controls, and update to a patched version if available beyond 4.0-24.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14771 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-14771 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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