CVE-2018-7241
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 · uneditedHard coded accounts exist in Schneider Electric's Modicon Premium, Modicon Quantum, Modicon M340, and BMXNOR0200 controllers in all versions of the communication modules.
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 confidenceHardcoded authentication credentials are embedded in the firmware of Schneider Electric Modicon Premium, Modicon Quantum, Modicon M340, and BMXNOR0200 PLC communication modules. Attackers with network access can use these accounts to gain unauthorized administrative access to the controllers.
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 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.
-
Identify affected PLC models in your environmentInventory your industrial control system equipment and identify if any Schneider Electric BMXNOR0200, BMXNOR0200h, or 140cpu* series controllers (140cpu65150, 140cpu31110, 140cpu43412u, 140cpu65160, 140cpu65260, 140cpu65860) are deployedAffected if Any of the listed models are present in the environment
-
Determine firmware version of affected modulesAccess the controller via the appropriate engineering software (Unity Pro, Somachine, or EcoStruxure) and retrieve the firmware version from the module properties or system informationAffected if The firmware version is any version (all versions are affected)
-
Verify network accessibility of PLCsCheck firewall rules, network segmentation, and access control lists to determine if the PLCs are reachable from untrusted networks or the internetAffected if The PLCs are directly accessible from networks outside the trusted control system zone
-
Test for presence of hardcoded accountsAttempt to authenticate to the PLC web interface or FTP service using the known hardcoded credentials (if documented in your security advisories) or check firmware configuration files for embedded credential stringsAffected if Authentication succeeds with any undocumented or hardcoded administrative account
-
Review authentication logs for unknown admin accessExamine controller event logs, syslog exports, or management platform logs for successful logins from IP addresses that are not recognized engineering workstationsAffected if Administrative access events appear from unexpected source addresses
You are affected if any Schneider Electric BMXNOR0200 or 140cpu* PLC modules are present in your environment and are network-accessible to untrusted parties, since the hardcoded credentials exist in all firmware versions.
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 access to industrial control systems, implement compensating controls such as firewalls and network segmentation, and contact Schneider Electric for patched firmware to replace the hardcoded accounts.
- Consultation12.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,632.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7241 — 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-2018-7241 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