dbcve.org
XhqApplication · Siemens

CVE-2019-13932

CRITICAL · 9.1 CVSS v3.1 Published 2019-12-12
Fix available
A fix is available. Upgrade to 6.0.0.2 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
A vulnerability has been identified in XHQ (All versions < V6.0.0.2). The web application requests could be manipulated, causing the the application to behave in unexpected ways for legitimate users. Successful exploitation does not require for an attacker to be authenticated. A successful attack could allow the import of scripts or generation of malicious links. This could allow the attacker to read or modify contents of the web application. At the time of advisory publication no public exploitation of this security vulnerability was known.

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 confidence

A request manipulation vulnerability in XHQ web application (versions < V6.0.0.2) allows unauthenticated attackers to manipulate web requests, enabling script import or malicious link generation. This can lead to unauthorized read/write access to the web application's contents.

MitigationUpgrade XHQ to version V6.0.0.2 or later to patch the request validation vulnerability. If immediate patching is not possible, restrict external access to the web application interface as a compensating control.

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
XhqApplication
Affected:< 6.0.0.2

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
None

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

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

  1. Locate XHQ installation and version
    Check the web application interface, typically accessed via browser, or check system documentation for version information. The version is usually displayed in the application header, about page, or login screen.
    Affected if The displayed version is lower than V6.0.0.2 (for example, V6.0.0.1, V5.x.x, or any version number below 6.0.0.2).
  2. Confirm web application is accessible
    Attempt to reach the XHQ web interface via HTTP/HTTPS from a browser or command line tool (curl, wget). Check if the login or main page loads.
    Affected if The web interface is reachable and responds to requests, meaning the attack surface exists.
  3. Inspect HTTP response headers
    Use browser developer tools or curl -I command to examine response headers from the XHQ server. Look for server version information in headers like Server, X-Powered-By, or similar fields.
    Affected if Version information in headers or the application itself shows a version below V6.0.0.2.
  4. Check for external exposure
    Review network configuration, firewall rules, or reverse proxy settings to determine if the XHQ web interface is accessible from untrusted networks or the internet.
    Affected if The web interface is exposed to external/untrusted networks without proper access restrictions.

A user is affected if their installed XHQ version is any version below V6.0.0.2 AND the web application interface is accessible, enabling unauthenticated request manipulation.

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.

dbcve · scoped
Upgrade available Upgrade to 6.0.0.2 or later
Fixed in 6.0.0.2
Interim mitigation

Upgrade XHQ to version V6.0.0.2 or later to patch the request validation vulnerability. If immediate patching is not possible, restrict external access to the web application interface as a compensating control.

Recommended fix High confidence

V6.0.0.2

  1. Back up current XHQ installation and configuration data
  2. Download XHQ version V6.0.0.2 from the official Siemens CERT portal or support channel
  3. Stop the XHQ service before applying the upgrade
  4. Install or apply the V6.0.0.2 upgrade following standard deployment procedures
  5. Restart the XHQ service after upgrade completion
  6. Verify the application is functioning correctly and the version is reported as V6.0.0.2

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Xhq Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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