CVE-2018-14935
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 · uneditedThe Web administration console on Polycom Trio devices with software before 5.5.4 has XSS.
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 Web administration console of Polycom Trio conference devices. The vulnerability exists in versions prior to 5.5.4 and allows attackers to inject malicious scripts through the admin 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< 5.5.4CVSS 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.
-
Identify Polycom Trio 8500 devices on the networkScan network for devices with Polycom Trio hostname or MAC OUI, or check your device inventory/MDNS for Polycom Trio 8500 conference phonesAffected if Device is not a Polycom Trio 8500 (other Polycom models have separate CVEs)
-
Access the Web administration consoleOpen a browser and navigate to the device IP address using HTTPS (e.g., https://<device-ip>) and log in with admin credentialsAffected if Web admin console is not accessible or you cannot authenticate (vulnerability requires access to this interface)
-
Locate the firmware version informationIn the Web admin console, navigate to System Information or About page - the firmware version is typically displayed on the dashboard or in the Status sectionAffected if Cannot determine version from the interface - try checking via device diagnostic page at https://<device-ip>/diagnostics.html or contacting Polycom support
-
Compare firmware version against 5.5.4Note the firmware version shown (format typically like 5.5.x.x) and check if the numeric version is less than 5.5.4Affected if Firmware version is 5.5.3, 5.5.2, 5.5.1, 5.5.0 or any earlier version - these are all vulnerable to CVE-2018-14935
You are affected if you have a Polycom Trio 8500 device with Web admin console accessible and firmware version prior to 5.5.4.
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 data5.5.4
Update Polycom Trio firmware to version 5.5.4 or later to remediate the XSS vulnerability.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14935 — 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-2018-14935 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