CVE-2019-6835
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 Cross-Site Scripting (XSS) CWE-79 vulnerability exists in U.motion Server (MEG6501-0001 - U.motion KNX server, MEG6501-0002 - U.motion KNX Server Plus, MEG6260-0410 - U.motion KNX Server Plus, Touch 10, MEG6260-0415 - U.motion KNX Server Plus, Touch 15), which could allow an attacker to inject client-side script when a user visits a web page.
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 confidenceA stored or reflected Cross-Site Scripting (XSS) vulnerability in Schneider Electric's U.motion Server allows remote attackers to inject malicious JavaScript or HTML through vulnerable input fields. When authenticated users access crafted URLs or malformed content, the injected script executes in their browser context, potentially stealing session cookies or performing actions on behalf of the user.
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< 1.3.7< 1.3.7< 1.3.7< 1.3.7CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 U.motion Server product modelAccess the device administrative interface or check device documentation. Look for model numbers Meg6501 or Meg6260 in the system information or device label.Affected if The device is a Schneider Electric Meg6501 (any variant) or Meg6260 (any variant)
-
Check installed firmware versionLog into the U.motion Server administrative interface. Navigate to System Settings, About, or Firmware Information section to view the currently installed firmware version. Alternatively, use the device's web API or command-line interface if available.Affected if Firmware version is below 1.3.7 (for example, 1.3.6, 1.3.5, etc.) or cannot be determined
-
Verify web interface is enabledAttempt to access the U.motion Server web interface via HTTP/HTTPS on the expected ports (commonly 80/443 or vendor-default ports). Confirm the login page or user dashboard loads.Affected if The web management interface is accessible and operational
-
Confirm authentication is in useCheck if the U.motion Server requires user authentication. Verify that user accounts are configured and the login form is present.Affected if Authentication is enabled and users can log in to the web interface
The environment is affected if the device is a Schneider Electric Meg6501 or Meg6260 with firmware version below 1.3.7 and the web interface is accessible with authentication 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 data1.3.7
Implement robust input validation and context-aware output encoding on all user-supplied data. Additionally, deploy Content Security Policy (CSP) headers to mitigate XSS execution. For existing deployments, apply vendor-supplied patches immediately.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6835 — 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-2019-6835 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