dbcve.org
Wire WebappApplication · Wire

CVE-2022-29168

MEDIUM · 6.1 CVSS v3.1 Published 2022-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Wire is a secure messaging application. Wire is vulnerable to arbitrary HTML and Javascript execution via insufficient escaping when rendering `@mentions` in the wire-webapp. If a user receives and views a malicious message, arbitrary code is injected and executed in the context of the victim allowing the attacker to fully control the user account. Wire-desktop clients that are connected to a vulnerable wire-webapp version are also vulnerable to this attack. The issue has been fixed in wire-webapp 2022-05-04-production.0 and is already deployed on all Wire managed services. On-premise instances of wire-webapp need to be updated to docker tag 2022-05-04-production.0-v0.29.7-0-a6f2ded or wire-server 2022-05-04 (chart/4.11.0) or later. No known workarounds exist.

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 confidence

Stored XSS vulnerability in Wire webapp's @mentions rendering feature allows attackers to inject malicious HTML/JavaScript into messages. When victims view these messages, the injected code executes in their browser context, enabling full account takeover.

MitigationUpdate wire-webapp to version 2022-05-04-production.0 or later (on-premise: docker tag 2022-05-04-production.0-v0.29.7-0-a6f2ded or wire-server 2022-05-04/chart-4.11.0). No workarounds available.

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
Wire WebappApplication
Affected:= 2016-07-29-17-00= 2016-08-04-15-44= 2016-08-23-09-31= 2016-08-24-10-10= 2016-08-29-14-54= 2016-09-08-15-38= 2016-09-19-14-01= 2016-09-28-14-58= 2016-10-11-15-34= 2016-10-18-08-10= 2016-10-25-08-17= 2016-10-26-18-58

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Wire Webapp version
    Locate the wire-webapp package or docker container and retrieve its version. For Docker, check the image tag; for package installations, check the package metadata or application settings.
    Affected if The installed version matches any of the following: 2016-07-29-17-00, 2016-08-04-15-44, 2016-08-23-09-31, 2016-08-24-10-10, 2016-08-29-14-54, 2016-09-08-15-38, 2016-09-19-14-01, 2016-09-28-14-58, 2016-10-11-15-34, 2016-10-18-08-10, 2016-10-25-08-17, 2016-10-26-18-58
  2. Verify @mentions feature is active
    Confirm that the @mentions functionality is enabled in the Wire Webapp configuration or that users are actively using @mentions in conversations.
    Affected if @mentions feature is enabled and users can create or view messages containing @mentions
  3. Review message content for suspicious @mentions
    Inspect recent messages in conversations or examine stored message data for any @mentions containing unusual HTML, JavaScript, or script-like patterns.
    Affected if Malicious @mentions with embedded scripts or HTML attributes are present in stored messages

If the Wire Webapp version matches one of the affected versions and the @mentions feature is enabled, the environment is vulnerable to stored XSS via @mentions rendering.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update wire-webapp to version 2022-05-04-production.0 or later (on-premise: docker tag 2022-05-04-production.0-v0.29.7-0-a6f2ded or wire-server 2022-05-04/chart-4.11.0). No workarounds available.

Recommended fix High confidence

wire-webapp 2022-05-04-production.0 / wire-server 2022-05-04 (chart/4.11.0) or later

  1. Identify the current Wire Webapp or Wire Server version running in your on-premise environment
  2. For Wire Webapp standalone: Upgrade to version 2022-05-04-production.0 or later
  3. For Docker deployments: Update to docker tag 2022-05-04-production.0-v0.29.7-0-a6f2ded or later
  4. For Wire Server: Upgrade to version 2022-05-04 (chart/4.11.0) or later
  5. Verify the upgrade was successful by checking the version and testing mention rendering
Caveat Review Wire release notes for breaking changes between your current version and 2022-05-04

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wire Webapp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29168 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-29168 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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