CVE-2017-7907
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 Improper XML Parser Configuration issue was discovered in Schneider Electric Wonderware Historian Client 2014 R2 SP1 and prior. An improperly restricted XML parser (with improper restriction of XML external entity reference, or XXE) may allow an attacker to enter malicious input through the application which could cause a denial of service or disclose file contents from a server or connected network.
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 confidenceThis is an XML External Entity (XXE) injection vulnerability in Schneider Electric Wonderware Historian Client 2014 R2 SP1 and prior versions. The application's XML parser is improperly configured without restrictions on XML external entity references, allowing attackers to inject malicious XML input. This can lead to denial of service attacks or unauthorized disclosure of file contents from the server or connected network.
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<= 2014_r2CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/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.
-
Verify Wonderware Historian Client installationCheck for the presence of Wonderware Historian Client software on the system. Look in Program Files for 'Schneider Electric' or 'Wonderware' folders, or check Add/Remove Programs for the installed application.Affected if Wonderware Historian Client is found installed on the system
-
Identify installed versionLocate the installed version of Wonderware Historian Client. Check program files directory, application properties, or version information in the Windows registry under the application's uninstall entry.Affected if The installed version is 2014_r2 or any prior version (including 2014_r2_sp1 and earlier)
-
Confirm XML parser usageDetermine if the Wonderware Historian Client processes XML input. Review application configuration files or log files for XML parsing activity, or monitor for .xml file handling by the application.Affected if The application processes or parses XML files as part of its normal operation
-
Check XML parser configurationExamine the application's XML parser configuration settings for external entity processing. Look for parser configuration files in the installation directory or application data folders that control XML entity resolution.Affected if The XML parser is configured to allow external entity references (DTD processing enabled)
-
Review network exposureAssess whether the Wonderware Historian Client is accessible over the network or accepts XML input from untrusted sources. Check firewall rules and application network listening status.Affected if The client accepts XML input from network sources without validation
A system is affected if it has Wonderware Historian Client version 2014_r2 or prior installed and the application processes XML input with external entity processing 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 dataDisable XML external entity processing in the application's XML parser configuration, or implement proper input validation to reject XML documents containing external entity declarations. If possible, upgrade to a patched version of Wonderware Historian Client.
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7907 — 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-2017-7907 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