CVE-2025-55996
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 · uneditedViber Desktop 25.6.0 is vulnerable to HTML Injection via the text parameter of the message compose/forward interface
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 confidenceViber Desktop 25.6.0 is vulnerable to HTML injection via the text parameter in the message compose/forward interface. An attacker could craft malicious HTML content that gets rendered when messages are composed or forwarded, potentially leading to script execution or visual manipulation.
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<= 25.6.0CVSS 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
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
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.
-
Check Viber Desktop versionOpen Viber Desktop and navigate to Settings > About, or use system tools like Add/Remove Programs (Windows) or Applications folder (Mac) to view the installed versionAffected if The installed version is 25.6.0 or lower
-
Verify message compose/forward interface existsOpen a conversation in Viber Desktop and locate the text input area where new messages are composed or existing messages are forwardedAffected if The message compose/forward text input field is present and accepts user-supplied text
-
Test HTML rendering in compose fieldEnter raw HTML tags (such as <b>test</b>, <i>italic</i>, or <img src=x>) into the message compose field and observe whether they are rendered as formatted HTML or displayed as plain textAffected if HTML tags are rendered as styled/functional HTML elements rather than being displayed as raw text
-
Check for script executionIn the compose field, attempt to enter a script tag like <script>alert(1)</script> or an event handler like <img src=x onerror=alert(1)> and trigger message composition or forwarding to see if the script executesAffected if JavaScript executes or the browser/chat interface processes the injected HTML code
A user is affected if their installed Viber Desktop version is 25.6.0 or below AND the message compose/forward interface renders HTML markup as active code instead of escaping it.
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 dataThe vendor should implement proper HTML encoding/sanitization of user-supplied text in the message compose/forward interface. Users should update to a patched version once released by Rakuten Viber.
- Consultation4.0 h
- Implementation16.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55996 — 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-2025-55996 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