CVE-2016-5815
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 · uneditedAn issue was discovered on Schneider Electric IONXXXX series power meters ION73XX series, ION75XX series, ION76XX series, ION8650 series, ION8800 series, and PM5XXX series. No authentication is configured by default. An unauthorized user can access the device management portal and make configuration changes.
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 · high confidenceSchneider Electric IONXXXX series power meters (ION73XX, ION75XX, ION76XX, ION8650, ION8800, PM5XXX series) ship with no authentication configured by default, allowing unauthenticated remote attackers to access the device management portal and modify device configurations.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model and seriesIdentify the Schneider Electric power meter model by checking the device label, web interface banner, or SNMP sysDescr. Confirm it is one of: Ion5000, Ion7300, Ion7500, Ion7600, Ion8650, or Ion8800.Affected if The device is any of the listed models in the IONXXXX series.
-
Check if authentication is required for web portal accessAttempt to access the device management web interface (typically HTTP/HTTPS on ports 80, 443, or 8080). Observe whether a login prompt appears immediately or if the management interface is fully accessible without entering credentials.Affected if The management portal loads and allows navigation through configuration screens without requiring any username or password.
-
Verify authentication configuration statusIf access is possible without credentials, check for any authentication-related settings within the web interface (such as user accounts, security settings, or access control configuration pages). Look for indicators that authentication is disabled or set to 'none'.Affected if The interface shows authentication as disabled, no user accounts are configured, or there is no password prompt at any point.
-
Test remote network access to management interfaceFrom an external network segment (not on the device's trusted management VLAN), attempt to reach the device web interface via its IP address. Confirm whether the full management portal is reachable without authentication from an untrusted network location.Affected if The device management interface is accessible remotely without authentication credentials.
A user is affected if their Schneider Electric IONXXXX power meter (Ion5000, Ion7300, Ion7500, Ion7600, Ion8650, or Ion8800) allows full access to the management portal without requiring any username or password, indicating authentication was never enabled.
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 dataEnable authentication on all affected power meters immediately, implement network segmentation to isolate industrial control devices from untrusted networks, and disable remote management access where not required.
- Consultation12.0 h
- Implementation16.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5815 — 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-2016-5815 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