CVE-2019-19288
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 vulnerability has been identified in XHQ (All Versions < 6.1). The web interface could allow Cross-Site Scripting (XSS) attacks if unsuspecting users are tricked into accessing a malicious link.
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 confidenceCross-Site Scripting (XSS) vulnerability in the XHQ web interface (all versions prior to 6.1) allows attackers to inject malicious scripts that execute in users' browsers when they access a crafted link, exploiting the lack of proper input sanitization or output encoding in the web application.
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< 6.1.0.0CVSS 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 XHQ installationLocate the XHQ web application on the system. Check for the XHQ installation directory, service, or running process. Common paths may include C:\Program Files\Siemens\XHQ or /opt/xhq on Linux systems. Look for the XHQ service in Windows Services or running processes.Affected if XHQ software is found running or installed on the system
-
Determine installed XHQ versionAccess the XHQ web interface login page or the administration console. Look for version information typically displayed in the About section, footer of the interface, or in the system administration panel. If web UI is unavailable, check version files in the installation directory.Affected if The installed version is anything earlier than 6.1.0.0 (for example, 6.0.x, 5.x, or older)
-
Verify web interface accessibilityDetermine if the XHQ web interface is accessible over HTTP/HTTPS. Check network configuration, firewall rules, or reverse proxy settings that expose the XHQ web portal to users or external networks.Affected if The XHQ web interface is exposed and accessible to users who could potentially click malicious links
-
Confirm lack of output encoding controlsInspect the XHQ configuration files or web server settings for any custom input validation, output encoding, or WAF configurations specifically addressing XSS protection. Check if the application uses standard security headers like Content-Security-Policy or X-XSS-Protection.Affected if No explicit XSS protection mechanisms (input sanitization, output encoding, security headers) are configured in the XHQ application
The environment is affected if XHQ version is installed and the web interface is accessible, with any version lower than 6.1.0.0 indicating direct vulnerability to this XSS flaw.
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 data6.1.0.0
Upgrade XHQ to version 6.1 or later to obtain the vendor patch; users should avoid clicking untrusted links as a temporary compensating control.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19288 — 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-19288 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