CVE-2019-6853
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 CWE-79: Failure to Preserve Web Page Structure vulnerability exists in Andover Continuum (models 9680, 5740 and 5720, bCX4040, bCX9640, 9900, 9940, 9924 and 9702) , which could enable a successful Cross-site Scripting (XSS attack) when using the products web server.
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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability (CWE-79) in the Andover Continuum web server. User-supplied input to the web interface is not properly sanitized or encoded, allowing attackers to inject malicious JavaScript code that executes in the context of other users' browsers when they view affected pages.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 the Andover Continuum device modelAccess the device management interface or check the device label/model number to confirm it is one of the following: 9680, 5740, 5720, Bcx4040, Bcx9640, 9900, 9940, or 9941Affected if The device is any of these Andover Continuum models
-
Verify the web server is enabledAttempt to access the Andover Continuum web interface by browsing to the device IP address on HTTP/HTTPS ports (typically 80/443). Check if the login page or web console loads.Affected if The web server responds and displays the Andover Continuum login or user interface
-
Confirm firmware versionLog into the web interface and navigate to the system information, status, or about page to view the installed firmware version. Alternatively, check via the device console or management software.Affected if The firmware version displayed matches any of the listed models (all versions are affected)
-
Locate user input fields in the web interfaceExplore the web interface for fields that accept user input such as user profiles, device naming, alarm messages, schedules, or system configuration areas where text can be entered and stored.Affected if The web interface contains input fields that store and display user-supplied data back to users
-
Verify if unsanitized input is stored and displayedEnter a harmless test string containing HTML characters (such as <script>alert(1)</script> or <b>test</b>) into available input fields, save the data, and then view the page where that data is displayed. Check if the raw characters are rendered or if HTML is interpreted.Affected if The entered test string is stored and displayed without proper encoding, indicating the XSS vulnerability exists
If the device is any Andover Continuum model (9680, 5740, 5720, Bcx4040, Bcx9640, 9900, 9940, or 9941) with the web server enabled and user input fields that store and display data without sanitization, the environment is affected by this stored XSS vulnerability.
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 firmware update when available. In the interim, restrict network access to the web server to trusted users only, and implement WAF rules to detect and block XSS payloads in HTTP requests.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6853 — 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-6853 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