CVE-2025-48397
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 · uneditedThe privileged user could log in without sufficient credentials after enabling an application protocol. This security issue has been fixed in the latest script patch latest version of of Eaton BLSS (7.3.0.SCP004).
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 confidenceA privileged user could authenticate without sufficient credentials after enabling an application protocol in Eaton BLSS, representing an authentication bypass vulnerability. The issue allows privilege escalation or unauthorized access due to improper credential validation when application protocols are enabled.
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
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Eaton BLSS is installedCheck system inventory, installed software list, or look for BLSS application directories and binaries. Common locations may include C:\Program Files\Eaton\BLSS or /opt/eaton/blss on Linux systems.Affected if Eaton BLSS software is present on the system
-
Determine the installed BLSS versionCheck the BLSS application version through its UI, about dialog, or version file in the installation directory. Compare against the fixed version 7.3.0.SCP004.Affected if The installed version is lower than 7.3.0.SCP004
-
Verify if application protocols are enabledAccess BLSS configuration settings and check whether any application protocols (such as Modbus, DNP3, or IEC 61850) have been enabled in the protocol configuration or network settings.Affected if Application protocols are enabled in the BLSS configuration
-
Review authentication logs for anomalous accessExamine BLSS authentication and access logs for any privileged user authentications that occurred after application protocols were enabled, looking for unauthorized access attempts or privilege escalation patterns.Affected if Privileged access occurred without proper credential validation after protocol enabling
A user is affected if Eaton BLSS is installed with a version lower than 7.3.0.SCP004 and has application protocols enabled, allowing potential authentication bypass and privilege escalation.
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 dataApply the latest patch (version 7.3.0.SCP004) to Eaton BLSS to remediate the authentication bypass. Verify proper credential enforcement after enabling any application protocols.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48397 — 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-48397 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