Ip Dect 110 FirmwareOperating system · Cisco
CVE-2023-20265
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 management interface of a small subset of Cisco IP Phones could allow an authenticated, remote attacker to conduct a stored cross-site scripting (XSS) attack against a user of the interface on an affected device. This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by persuading a user of an affected interface to view a page containing malicious HTML or script content. 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. To exploit this vulnerability, the attacker must have valid credentials to access the web-based management interface of the affected device.
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 stored cross-site scripting (XSS) vulnerability exists in the web-based management interface of certain Cisco IP Phones. An authenticated attacker with valid credentials can inject malicious HTML or script content that persists on the device. When other users access the affected interface, the malicious code executes in their browser context, potentially allowing arbitrary script execution and access to sensitive browser-based information.
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 Dect 110 FirmwareOperating system
< 5.1.2sr1
Ip Dect 210 FirmwareOperating system
< 5.1.2sr1
Unified Ip Phone 6901 FirmwareOperating system
>= 9.0, < 9.3\(1\)sr3
Unified Sip Phone 3905 FirmwareOperating system
>= 9.0, < 9.4\(1\)sr4CVSS 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.
-
Identify the Cisco IP Phone modelAccess the phone's web interface or check the device label/serial number to confirm the exact model (Ip Dect 110, Ip Dect 210, Unified Ip Phone 6901, or Unified Sip Phone 3905)Affected if The device is one of the four affected models listed in the CVE
-
Determine the firmware versionLog into the phone's web-based management interface and navigate to the About or Status page to view the firmware version, or use the phone's keypad to access system informationAffected if The firmware version falls outside the fixed versions: Ip Dect 110/210 at < 5.1.2sr1, Unified Ip Phone 6901 at < 9.3(1)sr3, or Unified Sip Phone 3905 at < 9.4(1)sr4
-
Verify web-based management interface is enabledCheck the phone's administration settings to confirm the HTTP/HTTPS web management interface is turned onAffected if Web-based management is enabled - the XSS only affects users who access this interface
-
Review stored configuration or user input fieldsExamine the web interface for any fields that accept user input and persist data (such as device name, contact info, or admin notes) to see if malicious script content may have been injectedAffected if Suspicious HTML or script tags are present in stored configuration fields that could execute when other users view the interface
A user is affected if they have a Cisco Ip Dect 110/210, Unified Ip Phone 6901, or Unified Sip Phone 3905 running a firmware version below the fixed releases AND the web-based management interface is enabled and accessible.
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.
dbcve · scoped5.1.2sr19.39.4
Apply Cisco-provided patches/updates for affected IP Phone models when available; restrict access to the web-based management interface to trusted administrators; disable web-based management if not required.
Ip Dect 110/210: upgrade to 5.1.2sr1 or later | Unified Ip Phone 6901: upgrade to 9.3(1)sr3 or later | Unified Sip Phone 3905: upgrade to 9.4(1)sr4 or later
- 1. Identify the exact model of the affected Cisco IP phone (Ip Dect 110, Ip Dect 210, Unified Ip Phone 6901, or Unified Sip Phone 3905)
- 2. Access the device's web-based management interface using valid administrator credentials
- 3. Navigate to the firmware version or administration section of the web interface
- 4. Download the appropriate fixed firmware version from Cisco's official support site (sec.cloudapps.cisco.com) based on your device model
- 5. Upload and apply the firmware upgrade file through the web management interface, or use the device's firmware update utility
- 6. After the upgrade completes, verify the new firmware version matches the fixed release (5.1.2sr1 for DECT devices, 9.3(1)sr3 for Phone 6901, or 9.4(1)sr4 for Phone 3905)
- 7. Confirm the upgrade was successful by logging back into the web interface and checking the firmware version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ip Dect 110 Firmware
Scoped from the published advisory
- 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-2023-20265 — 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-2023-20265 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