CVE-2025-9574
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 ALS-mini-s4 IP, ABB ALS-mini-s8 IP.This issue affects . All firmware versions with the Serial Number from 2000 to 5166
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 vulnerability in ABB ALS-mini-s4 IP and ALS-mini-s8 IP devices allows unauthenticated attackers to access critical functions. The issue affects all firmware versions with serial numbers 2000-5166, enabling remote unauthenticated access to sensitive operations.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm device model is affectedIdentify the ABB device model by checking the device label, web interface header, or management console. Look for ALS-mini-s4 IP or ALS-mini-s8 IP designations.Affected if The device is an ABB ALS-mini-s4 IP or ALS-mini-s8 IP model
-
Check device serial number rangeRetrieve the device serial number from the device label, web interface system info page, or management console. Compare the serial number to the affected range 2000-5166.Affected if The serial number falls within 2000-5166 inclusive
-
Verify network accessibility of management interfaceAttempt to access the device web interface or management port from an unauthorized network location without providing credentials. Check if the HTTP/HTTPS management interface is reachable.Affected if The device management interface is accessible from an untrusted network without authentication
-
Confirm critical functions accessible without authAccess the device web interface or API endpoints without logging in. Attempt to reach sensitive operation pages or functions such as configuration, firmware, or diagnostic areas.Affected if Critical functions or sensitive operation pages are accessible without any authentication credentials
A user is affected if they have an ABB ALS-mini-s4 IP or ALS-mini-s8 IP device with a serial number between 2000 and 5166 that has its management interface accessible from an untrusted network without requiring 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 dataRestrict network exposure of affected devices via firewall rules and VLAN segmentation; contact ABB for patched firmware or compensating controls; assume compromise if devices are internet-facing.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9574 — 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-9574 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