CVE-2020-28210
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-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting) vulnerability exists in EcoStruxure Building Operation WebStation V2.0 - V3.1 that could cause an attacker to inject HTML and JavaScript code into the user's browser.
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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in Schneider Electric's EcoStruxure Building Operation WebStation versions 2.0 through 3.1. The application's web interface fails to properly sanitize user-supplied input before rendering it in HTML pages, allowing an attacker to inject malicious HTML and JavaScript code that executes in the context of other users' browsers.
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.0, <= 3.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
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 EcoStruxure Building Operation versionCheck the installed software version through the Windows Programs and Features list, or query the application's about dialog or version information file typically found in the installation directory (e.g., C:\Program Files\Schneider Electric\EcoStruxure Building Operation\)Affected if The installed version is greater than or equal to 2.0 and less than or equal to 3.1
-
Verify WebStation module is enabledAccess the EcoStruxure Building Operation system administrator interface and check if the WebStation web service is enabled and running. This is typically configured in the System > Services or System > Communication settings within the building management software.Affected if WebStation is enabled and accessible to users
-
Inspect web server configurationLocate the WebStation configuration files in the installation directory (commonly in a 'conf' or 'config' subfolder) and verify the web server is actively listening on the configured HTTP/HTTPS ports (default often 8080/8443 for local access).Affected if The web server is running and accepting connections
-
Review user input handling in web pagesLog into the WebStation interface and navigate to fields that accept user-supplied content such as device names, alarm annotations, schedule labels, or custom text entries. Submit test HTML or script tags (e.g., <script>alert(1)</script>) in these fields and check if the content is rendered as plain text or executed as code when viewed by other users.Affected if User-supplied input in WebStation is reflected back in HTML without sanitization or encoding
You are affected if EcoStruxure Building Operation version 2.0 to 3.1 is installed with WebStation enabled and user input fields in the web interface render unescaped HTML or JavaScript.
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 dataApply the vendor patch from Schneider Electric (SEBo-2020-287) to upgrade to version 3.2 or later. As a compensating control, implement input validation and output encoding on all user-controllable fields, and consider deploying a WAF to filter malicious requests until the patch can be applied.
- Consultation2.0 h
- Implementation8.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,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-28210 — 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-2020-28210 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