Ip Phone 6841 FirmwareOperating system · Cisco
CVE-2019-16008
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 in the web-based GUI of Cisco IP Phone 6800, 7800, and 8800 Series with Multiplatform Firmware could allow an authenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the web-based interface of an affected system. The vulnerability is due to insufficient validation of user-supplied input by the web-based GUI of an affected system. An attacker could exploit this vulnerability by persuading a user of the interface to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive, browser-based information.
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 confidenceStored XSS vulnerability in the web-based GUI of Cisco IP Phone 6800, 7800, and 8800 Series with Multiplatform Firmware. An authenticated attacker can inject malicious JavaScript via insufficiently validated user-supplied input, which executes in the context of a victim's browser when they access the affected 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
Ip Phone 6841 FirmwareOperating system
< 11.3\(1\)
Ip Phone 6851 FirmwareOperating system
< 11.3\(1\)
Ip Phone 6825 FirmwareOperating system
< 11.3\(1\)
Ip Phone 6861 FirmwareOperating system
< 11.3\(1\)
Ip Phone 6871 FirmwareOperating system
< 11.3\(1\)
Ip Phone 6821 FirmwareOperating system
< 11.3\(1\)
Ip Phone 7811 FirmwareOperating system
< 11.3\(1\)
Ip Phone 7821 FirmwareOperating system
< 11.3\(1\)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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Determine if the web-based GUI is enabledLog into the phone's administration interface and check the web server settings, or attempt to access the phone's HTTP/HTTPS management page from a browserAffected if The web GUI is accessible and enabled on the device
-
Identify the firmware version installedAccess the phone's web GUI status or administration page, typically found under 'Info' or 'System' settings, which displays the current firmware versionAffected if The displayed firmware version is lower than 11.3(1)
-
Confirm the phone model is in the affected product listCheck the physical device label or the web GUI for the model number (6841, 6851, 6825, 6861, 6871, 6821, 7811, 7821, or other 6800/7800/8800 series variants)Affected if The phone model matches any of the listed affected models and the firmware version is below 11.3(1)
-
Verify multiplatform firmware is in useCheck the firmware type in the phone's administration interface or release notes; multiplatform firmware is distinct from CUCM (CallManager) firmwareAffected if The phone runs multiplatform firmware (not CUCM firmware) and meets the version criteria
A user is affected if their Cisco IP Phone 6800/7800/8800 series runs multiplatform firmware below version 11.3(1) and has the web-based GUI enabled, allowing authenticated users to inject malicious scripts that execute in other users' browsers.
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 data11.3
Apply the vendor firmware update from Cisco. Until patched, restrict web GUI access to trusted users only and educate users about not clicking untrusted links.
Fix this in Ip Phone 6841 Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16008 — 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-16008 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