Debian LinuxOperating system · Debian
CVE-2019-13274
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 · uneditedIn Xymon through 4.3.28, an XSS vulnerability exists in the csvinfo CGI script due to insufficient filtering of the db parameter.
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 confidenceA reflected Cross-Site Scripting (XSS) vulnerability exists in the csvinfo CGI script of Xymon monitoring tool. The 'db' parameter is not properly sanitized or encoded before being reflected in the HTTP response, allowing an attacker to inject malicious JavaScript code that executes in the context of victim's browser session.
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
Debian LinuxOperating system
= 8.0<= 4.3.28CVSS 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.0/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.
-
Confirm Xymon is installedLocate the Xymon installation by checking common paths such as /usr/local/xymon, /opt/xymon, or running 'which xymon' and 'dpkg -l | grep xymon' on Debian systemsAffected if Xymon is not present on the system, the vulnerability does not apply
-
Determine the installed Xymon versionRun 'xymon --version' or check the version file in the Xymon installation directory (typically /usr/local/xymon/lib/version or /opt/xymon/lib/version)Affected if The installed version is 4.3.28 or lower, making it potentially vulnerable
-
Locate the csvinfo CGI scriptFind the csvinfo script in the Xymon cgi-bin directory, commonly at /usr/local/xymon/cgi-bin/csvinfo.cgi or /opt/xymon/cgi-bin/csvinfo.cgiAffected if The csvinfo CGI script does not exist, the vulnerability cannot be exploited
-
Verify the 'db' parameter handling in csvinfoExamine the csvinfo.cgi source code for the 'db' parameter usage - search for code that reads the 'db' parameter (e.g., using $QUERY_STRING, CGI param, or similar) and reflects it into output without sanitization or encodingAffected if The code reflects the 'db' parameter directly into the HTTP response without proper encoding or validation, the system is vulnerable
A system is affected if it runs Xymon version 4.3.28 or lower with the csvinfo CGI script accessible and the 'db' parameter reflected in the response without sanitization.
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 dataApply the vendor patch (upgrade to Xymon 4.3.29 or later). If immediate patching is not possible, implement input validation and output encoding on the 'db' parameter in the csvinfo CGI script.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13274 — 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-13274 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