Repetier ServerApplication

CVE-2019-14451

CRITICAL · 9.8 CVSS v3.1 Published 2019-10-25
Fix available
A fix is available. Upgrade to after 0.91 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
RepetierServer.exe in Repetier-Server 0.8 through 0.91 does not properly validate the XML data structure provided when uploading a new printer configuration. When this is combined with CVE-2019-14450, an attacker can upload an "external command" configuration as a printer configuration, and achieve remote code execution. After exploitation, loading of the external command configuration is dependent on a system reboot or service restart.

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

The RepetierServer.exe in Repetier-Server versions 0.8 through 0.91 fails to properly validate XML data structures during printer configuration uploads. Combined with CVE-2019-14450, this allows attackers to upload malicious 'external command' configurations as printer configurations, achieving persistent remote code execution that activates after system reboot or service restart.

MitigationUpgrade Repetier-Server to a version beyond 0.91 which contains proper XML validation and blocks external command configuration uploads. If immediate patching is not possible, restrict network access to the Repetier-Server administration interface.

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
Repetier ServerApplication
Affected:>= 0.80, <= 0.91

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

CVSS:3.1/AV:N/AC:L/PR:N/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 if Repetier-Server is installed
    Look for RepetierServer.exe in running processes or check for the Repetier-Server service. On Windows, check Services list or Task Manager. On Linux, check for repetier-server process.
    Affected if RepetierServer.exe process or service is found running on the system
  2. Determine installed version
    Access the Repetier-Server web interface and check the server version displayed on the main dashboard, or check the application logs. Compare the version number against the affected range >= 0.80 and <= 0.91.
    Affected if The installed version falls within 0.80 through 0.91 inclusive
  3. Verify admin interface accessibility
    Check if the Repetier-Server web administration interface is accessible over the network. Attempt to access the web interface on the configured port (default 3344).
    Affected if The admin interface is reachable from network or untrusted locations
  4. Inspect printer configurations for external commands
    In the Repetier-Server web interface, navigate to Printer Configuration > Printer Settings. Look for any entries in fields related to 'external command', 'Gcode scripts', or 'custom commands' that contain unexpected or suspicious shell commands, scripts, or system calls.
    Affected if Any printer configuration contains custom external command entries that were not intentionally configured by an administrator

The system is affected if Repetier-Server version 0.80-0.91 is running and the XML validation flaw allows external command configurations to be uploaded as printer configurations.

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 a release after 0.91
Interim mitigation

Upgrade Repetier-Server to a version beyond 0.91 which contains proper XML validation and blocks external command configuration uploads. If immediate patching is not possible, restrict network access to the Repetier-Server administration interface.

Fix this in Repetier Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-14451 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-14451 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