CVE-2025-8754
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 · uneditedMissing Authentication for Critical Function vulnerability in ABB ABB AbilityTM zenon.This issue affects ABB AbilityTM zenon: from 7.50 through 14.
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 confidenceMissing Authentication for Critical Function vulnerability in ABB AbilityTM zenon allows unauthenticated access to a critical function. This affects versions 7.50 through 14. The lack of authentication enforcement on a sensitive operation could allow attackers to invoke protected functionality without credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Confirm ABB AbilityTM zenon installationCheck if ABB AbilityTM zenon software is installed on the system by reviewing installed programs in Windows Programs and Features, or by searching for zenon installation directories (commonly under C:\Program Files\ABB or C:\zenon).Affected if ABB AbilityTM zenon software is present on the system.
-
Identify installed zenon versionLocate the zenon version information. Check the zenon about dialog within the application, examine the zenon installation directory for version files, or query the Windows Registry under HKLM\SOFTWARE\ABB if available.Affected if The installed version cannot be determined or is within the 7.50 to 14 range.
-
Compare version against affected rangeIf the version is identified, compare it against the affected range: versions 7.50 through 14 are vulnerable. Any version at or above 7.50 and at or below 14 is in the affected range.Affected if The installed version is 7.50, 7.60, 7.70, 7.80, 8.0, 8.10, 8.20, 9.0, 10.0, 11.0, 12.0, 13.0, 14.0, or any intermediate version within this range.
-
Assess exposure of critical functionReview network exposure and access controls for the zenon system. Determine if the critical function (the specific unauthenticated endpoint or operation) is accessible from network locations outside the trusted zone.Affected if The zenon system and its critical functions are accessible from untrusted networks without authentication requirements.
The environment is affected if ABB AbilityTM zenon version 7.50 through 14 is installed and the vulnerable critical function is accessible without authentication.
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 dataUpgrade ABB AbilityTM zenon to a version beyond 14 that includes the security patch. If immediate patching is not possible, implement network segmentation and firewall rules to restrict access to the zenon system and monitor for unauthorized access attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8754 — 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-8754 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