CVE-2013-3957
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 · uneditedSQL injection vulnerability in the login screen in the Web Navigator in Siemens WinCC before 7.2 Update 1, as used in SIMATIC PCS7 8.0 SP1 and earlier and other products, allows remote attackers to execute arbitrary SQL commands via unspecified vectors.
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 confidenceSQL injection vulnerability in the Web Navigator login screen of Siemens WinCC before version 7.2 Update 1 allows remote attackers to execute arbitrary SQL commands. This affects SIMATIC PCS7 8.0 SP1 and earlier versions, enabling unauthenticated remote code execution via the database.
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<= 8.0= 8.0<= 7.2= 7.0= 7.1CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 installed Siemens WinCC versionLocate the WinCC installation and check the version information, typically found in the program files or registry entries for WinCC componentsAffected if The installed version is 7.0, 7.1, or 7.2 or any version below 7.2 Update 1
-
Identify installed SIMATIC PCS7 versionLocate the PCS7 installation and check the version information in the program files or registryAffected if The installed version is 8.0 SP1 or earlier (8.0, any version below 8.0)
-
Verify Web Navigator component statusCheck if the WinCC Web Navigator service or web application is installed and running on the systemAffected if Web Navigator is enabled and accessible, as the SQL injection vulnerability exists specifically in the Web Navigator login screen
-
Confirm version is within affected rangeCompare your installed WinCC or PCS7 version against the known affected ranges: WinCC 7.0, 7.1, or <=7.2; PCS7 <=8.0 or =8.0Affected if The version matches any of the affected versions listed in the CVE
You are affected if Siemens WinCC version 7.0, 7.1, or 7.2 (or any version below 7.2 Update 1) or SIMATIC PCS7 version 8.0 or earlier is installed AND the Web Navigator component is enabled and accessible.
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 dataUpdate Siemens WinCC Web Navigator to version 7.2 Update 1 or later to obtain the vendor patch. In the interim, restrict network access to the Web Navigator service and monitor for SQL injection attempts in logs.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3957 — 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-2013-3957 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