dbcve.org
T Mac PlusApplication · Abb

CVE-2025-14772

HIGH · 8.8 CVSS v3.1 Published 2026-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Authorization bypass through User-Controlled key 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 confidence

This is an authorization bypass vulnerability in ABB T-MAC Plus where the application improperly validates user-controlled keys (such as IDs, tokens, or parameters) when making authorization decisions. An attacker could manipulate these keys to access resources or functions they should not have permission to access, bypassing the application's access control mechanisms.

MitigationImplement proper server-side validation of all authorization keys and ensure authorization checks are performed on every sensitive operation regardless of user-controlled input. Apply vendor patches as soon as they become available for version 4.0-24.

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
T Mac PlusApplication
Affected:= 4.0-24

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checks

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

  1. Identify installed T-MAC Plus version
    Access the T-MAC Plus management interface or check the software installed on the system. Look for version information in the About section, system settings, or installed programs list. If using command-line tools, run: tmacplus -v or check the installer logs.
    Affected if The installed version is 4.0 through 4.0-24 (or version 4.0 build 24 or earlier)
  2. Locate T-MAC Plus web interface or API endpoints
    Identify if T-MAC Plus exposes a web-based management console, REST API, or other network service. Check for open ports (common web ports 80, 443, or custom ports) or review configuration files for service bindings.
    Affected if T-MAC Plus web interface or API is accessible on the network
  3. Review authorization logic for user-controlled parameters
    Examine application configuration files, access control policies, or custom scripts that define how user requests are authorized. Look for patterns where request parameters (such as IDs, keys, usernames, or session tokens) are used directly in authorization decisions without server-side validation.
    Affected if Authorization decisions rely on user-supplied input like IDs, keys, or parameters without independent permission verification
  4. Test for parameter tampering in access control
    If you have access to the application, attempt to modify ID values, keys, or parameters in requests to access resources outside your assigned permissions. Compare authorized versus unauthorized access attempts.
    Affected if Modifying user-controlled parameters allows access to resources or functions not assigned to the current user

You are affected if T-MAC Plus version is 4.0-24 or earlier AND the application uses user-supplied parameters (IDs, keys, or other input) as the sole basis for making authorization decisions without independent permission validation.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper server-side validation of all authorization keys and ensure authorization checks are performed on every sensitive operation regardless of user-controlled input. Apply vendor patches as soon as they become available for version 4.0-24.

Fix this in T Mac Plus Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14772 — 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-14772 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