dbcve.org
Meg6501 0001 FirmwareOperating system · Schneider Electric

CVE-2019-6839

HIGH · 8.8 CVSS v3.1 Published 2019-09-17
Fix available
A fix is available. Upgrade to 1.3.7 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A CWE-434: Unrestricted Upload of File with Dangerous Type 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 a user with low privileges to upload a rogue file.

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 confidence

A CWE-434 unrestricted file upload vulnerability exists in U.motion Server (MEG6501-0001, MEG6501-0002, MEG6260-0410, MEG6260-0415), allowing low-privilege users to upload files with dangerous types/extensions that could lead to remote code execution or server compromise.

MitigationImplement strict file type validation (both by extension and MIME type), restrict uploaded files to a non-executable directory outside the web root, and enforce role-based access controls limiting file upload permissions to authorized users only.

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
Meg6501 0001 FirmwareOperating system
Affected:< 1.3.7
Meg6501 0002 FirmwareOperating system
Affected:< 1.3.7
Meg6260 0410 FirmwareOperating system
Affected:< 1.3.7
Meg6260 0415 FirmwareOperating system
Affected:< 1.3.7

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the U.motion Server model
    Access the device web interface or check the product label/serial number. Look for model numbers MEG6501-0001, MEG6501-0002, MEG6260-0410, or MEG6260-0415.
    Affected if The model is one of the four affected variants listed in the CVE.
  2. Determine the installed firmware version
    Log into the U.motion Server administration interface and navigate to System > Status or System > Firmware. Note the firmware version number.
    Affected if The firmware version is lower than 1.3.7 (for example, 1.3.6, 1.3.5, 1.2.x, etc.).
  3. Verify if file upload functionality exists
    Navigate through the web interface to find any file upload, backup/restore, or import features. Look for pages labeled Upload, Import, Backup, or similar.
    Affected if The interface exposes a file upload feature (such as a backup restore or configuration import function).
  4. Check user role permissions for upload access
    Access the User Management or Access Control section of the admin interface. Review which user roles have permission to use file upload or import functions.
    Affected if Low-privilege users (non-admin roles) are granted permission to access file upload or import features.
  5. Inspect file type validation configuration
    Look for settings related to file upload restrictions, file type validation, or allowed extensions in the system configuration or security settings.
    Affected if No file type validation is configured, or the system accepts dangerous extensions such as .php, .exe, .sh, .asp, .jsp, or .html for upload.

Your environment is affected if you run any of the listed models with firmware version below 1.3.7 and the file upload feature is accessible to low-privilege users without strict file type restrictions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 1.3.7 or later
Fixed in 1.3.7
Interim mitigation

Implement strict file type validation (both by extension and MIME type), restrict uploaded files to a non-executable directory outside the web root, and enforce role-based access controls limiting file upload permissions to authorized users only.

Fix this in Meg6501 0001 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-6839 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-6839 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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