CVE-2023-37200
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 · uneditedA CWE-611: Improper Restriction of XML External Entity Reference vulnerability exists that could cause loss of confidentiality when replacing a project file on the local filesystem and after manual restart of the server.
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 XXE (XML External Entity) vulnerability (CWE-611) in project file handling. An attacker with local filesystem access can replace a project configuration file with a malicious XML file containing external entity references, and after a manual server restart, the parser will resolve these entities, allowing unauthorized read access to sensitive files on the local system.
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< 2.01= 2.01CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 product and versionLocate Se Ecostruxure Opc Ua Server Expert installation and retrieve the version number from the application, typically via 'Add/Remove Programs', the application's 'About' dialog, or checking version info on the executableAffected if Version is 2.01 or any version lower than 2.01 (e.g., 1.x)
-
Locate project configuration filesSearch for XML project configuration files used by the application - look in the application's data directory, projects folder, or user-specified project locations for .xml files that store project settingsAffected if XML project configuration files exist and are writable by the user (attacker needs filesystem write access to replace them)
-
Check XML parser security configurationIf source code or configuration files are accessible, examine XML parser initialization code or configuration for settings that control external entity resolution - look for flags like 'DTD', 'external entities', or 'XXE' in parser configurationAffected if XML parsers are configured to allow external entities or DTD processing (no XXE protection is enabled)
-
Verify server restart requirementConfirm the application runs as a service or daemon that requires manual restart to reload configuration files - check if project files are loaded at startup rather than dynamicallyAffected if The application requires a manual restart to reload project configuration changes, meaning replaced malicious files will be parsed after restart
You are affected if the installed version is 2.01 or any version below 2.01, and XML project configuration files exist in writable locations where an attacker could replace them with malicious XXE payloads.
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.
dbcve · scoped2.01
Disable external entity resolution in XML parsers by configuring parsers to reject DTDs and external entities, or use a parser that has XXE protection enabled by default.
Ecoustic Opc Ua Server Expert version 2.02 or later
- 1. Navigate to the Schneider Electric download portal at download.schneider-electric.com
- 2. Locate Ecostruxure Opc Ua Server Expert in the product catalog
- 3. Download version 2.02 or later (the first release that includes the security fix for CVE-2023-37200)
- 4. Before upgrading, backup all existing project files and server configurations
- 5. Stop the Ecostruxure Opc Ua Server Expert service
- 6. Install the new version (2.02 or later) following the standard installation procedure
- 7. Restore the backed-up project files to the appropriate location on the local filesystem
- 8. Restart the server service to apply the changes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37200 — 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-2023-37200 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