CVE-2020-10633
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 non-persistent XSS (cross-site scripting) vulnerability exists in eWON Flexy and Cosy (all firmware versions prior to 14.1s0). An attacker could send a specially crafted URL to initiate a password change for the device. The target must introduce the credentials to the gateway before the attack can be successful.
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 confidenceA non-persistent (reflected) cross-site scripting vulnerability in eWON Flexy and Cosy industrial VPN gateways allows attackers to inject malicious scripts via specially crafted URLs targeting the password change functionality. The attack is non-persistent, requires user interaction (target must enter credentials), and affects all firmware versions prior to 14.1s0.
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< 14.1s0< 14.1s0CVSS 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 the eWON device modelAccess the device web interface or check the device label/documentation to confirm it is an eWON Flexy or Cosy industrial VPN gatewayAffected if The device is not an eWON Flexy or Cosy gateway - this CVE does not apply
-
Determine the firmware versionLog into the eWON web interface and navigate to the status or system information page to view the installed firmware version, or use the eWON configuration tool to check the firmware versionAffected if Unable to determine the firmware version - further investigation needed
-
Compare firmware version to affected rangeCheck if the installed firmware version is less than 14.1s0. The version number is typically displayed as a format like xx.xs0 (e.g., 13.3s0, 14.0s0)Affected if Firmware version is 14.1s0 or later - the device is NOT affected. Firmware version is below 14.1s0 - the device IS affected
-
Verify password change functionality is accessibleCheck if the web-based password change interface is accessible on the device. This is typically found in the Administration or Security settings section of the eWON web interfaceAffected if The password change functionality is not accessible or not enabled, the XSS attack surface may be reduced but the vulnerability still exists in the code if firmware is < 14.1s0
The environment is affected if the device is an eWON Flexy or Cosy gateway running firmware version prior to 14.1s0, regardless of whether the password change interface is currently 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 data14.1s0
Upgrade eWON Flexy/Cosy firmware to version 14.1s0 or later to patch the XSS vulnerability in the password change mechanism.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10633 — 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-10633 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