CVE-2026-5922
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 IP phone might use malicious input stored in configuration parameters and render it as content for the WebUI’s webpage.
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 in IP phone firmware where malicious input saved in configuration parameters gets rendered as unescaped HTML/JavaScript content in the WebUI, allowing attackers to execute scripts in the context of other users viewing the affected pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Authentication
- X
- User interaction
- P
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 IP phone model and firmware versionAccess the device admin page or check system information in the WebUI, or look at the device label/SIP banner to determine the exact model number and running firmware versionAffected if The firmware version is any version that has not been patched and contains the vulnerable WebUI configuration rendering code
-
Verify WebUI administrative interface is enabledAttempt to access the WebUI login page via HTTP/HTTPS on the device management port (commonly 80, 443, or 8080)Affected if The WebUI is accessible without being disabled or restricted
-
Confirm configuration parameter accessLog into the WebUI and navigate to the configuration or settings section where parameters such as device name, SIP credentials, or user preferences can be savedAffected if You can save custom values to configuration fields that are then displayed back in the WebUI
-
Check for unescaped rendering in displayed parametersIn the WebUI configuration pages, observe whether values you previously entered are rendered as raw HTML (for example, if entering <script> appears as script tags or executes) when viewing the settings pageAffected if Configuration values are displayed as unescaped HTML/JavaScript content rather than being properly encoded
-
Determine multi-user access scopeVerify whether other users or administrators can access the same WebUI pages where configuration parameters are displayedAffected if Multiple users view the same configuration pages where malicious stored scripts would execute in their browser context
Your environment is affected if the IP phone has a WebUI with configuration parameters that render user-supplied input as unescaped HTML, allowing stored XSS to execute when other users view those pages.
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 vendor firmware updates when available; until then, disable or restrict access to the WebUI administrative interface and implement input validation/output encoding on any custom configurations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5922 — 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-2026-5922 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