CVE-2018-7760
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 authorization bypass vulnerability exists in Schneider Electric's Modicon M340, Modicon Premium, Modicon Quantum PLC, BMXNOR0200. Requests to CGI functions allow malicious users to bypass authorization.
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 confidenceAn authorization bypass vulnerability in Schneider Electric's Modicon M340, Modicon Premium, Modicon Quantum PLC, and BMXNOR0200 allows malicious users to bypass authentication by sending requests directly to CGI functions, potentially granting unauthorized access to PLC management interfaces.
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 the PLC modelCheck the device physical label, or query the PLC through the management interface or engineering workstation software to determine the exact model number (e.g., BMXNOR0200, 140cpu65150, etc.)Affected if The model matches one of the affected products: BMXNOR0200, BMXNOR0200h, 140cpu65150, 140cpu31110, 140cpu43412u, 140cpu65160, 140cpu65260, or 140cpu65860
-
Confirm the firmware versionAccess the PLC web interface (if enabled) or use the engineering software to retrieve the firmware version informationAffected if Any firmware version is installed, since the advisory states all versions are affected
-
Verify the web interface is enabledCheck the PLC network configuration through the engineering workstation or by attempting to reach the device IP on HTTP/HTTPS ports (typically ports 80/443 or 8080/8443)Affected if The web management interface is accessible on the network, which enables the CGI function attack surface
-
Test CGI endpoint accessibilitySend a direct HTTP request to a known CGI endpoint on the PLC (such as /cgi/bin/ or specific CGI scripts used for PLC management) without providing authentication credentialsAffected if CGI endpoints respond without requiring authentication, indicating the authorization bypass is present
-
Check network exposure of the PLC web interfaceReview firewall rules, network segmentation, and access control lists to determine if the PLC web management ports are reachable from untrusted network segments or the internetAffected if The PLC web interface is reachable from networks that should not have management access
A user is affected if they have any of the listed PLC models with the web interface enabled and exposed to networks where unauthorized CGI access is possible.
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 PLC web interfaces using network segmentation, implement proper authorization enforcement on all CGI endpoints, and apply vendor-provided patches when released.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7760 — 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-7760 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