CVE-2012-3013
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 · uneditedWAGO I/O System 758 model 758-870, 758-874, 758-875, and 758-876 Industrial PC (IPC) devices have default passwords for unspecified Web Based Management accounts, which makes it easier for remote attackers to obtain administrative access via a TCP session.
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 confidenceWAGO I/O System 758 industrial PC devices (models 758-870, 758-874, 758-875, 758-876) contain default passwords for Web-Based Management (WBM) accounts, enabling remote attackers to gain administrative access via TCP sessions.
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 data= 758-870= 758-874= 758-875= 758-876CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 device modelCheck the label or firmware identification of the WAGO I/O System 758 device to confirm the exact model number (758-870, 758-874, 758-875, or 758-876)Affected if The device model matches one of the affected models: 758-870, 758-874, 758-875, or 758-876
-
Verify WBM interface accessibilityAttempt to access the Web-Based Management interface by entering the device IP address in a web browser over HTTP (port 80) or HTTPS (port 443)Affected if The WBM login page loads and is accessible over the network, indicating WBM is enabled
-
Test for default credentialsAttempt to log in to the WBM interface using the known default credentials for WAGO devices (typically admin/admin or administrator/administrator, or check WAGO documentation for the specific default username/password pairs)Affected if Login succeeds with default credentials, confirming the default password vulnerability is present
-
Check network exposure of management interfaceDetermine if the WBM port (80/443) is listening on externally accessible network interfaces by reviewing network configuration or performing a port scan from an external locationAffected if The WBM interface is reachable from non-trusted network segments or the internet
The environment is affected if the device is a WAGO 758-870, 758-874, 758-875, or 758-876 model with WBM enabled and default credentials still in use, particularly if the management interface is exposed to accessible networks.
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 dataImmediately change all default credentials on WBM interfaces, disable remote management access if not required, and implement network segmentation to limit exposure of management interfaces.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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 $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3013 — 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-2012-3013 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