Wire Webapp
Approved changes feed: RSS · Atom
cpe:2.3:a:wireapp:wire-webapp:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Wireapp (d04fd6f7-6e70-5472-9b75-3c59ffc0e9a7) |
|---|---|
| Product | Wire Webapp (356c33b9-3bef-5733-a3fd-f5c14e2c59c6) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-48066 |
vulnerable | 2026-06-08 07:27:15.437800 |
wire-webapp has no database deletion on client logout
MEDIUM (6)
wire-webapp is the web application for the open-source messaging service Wire. A bug fix caused a regression causing an issue with function to delete local data. Instructing the client to delete its local database on user logout does not result in deletion. This is the case for both temporary clients (marking the device as a public computer on login) and regular clients instructing the deletion of all personal information and conversations upon logout. Access to the machine is required to access the data. If encryption-at-rest is used, cryptographic material can't be exported. The underlying issue has been fixed with wire-webapp version 2025-05-14-production.0. In order to mitigate potential impact, the database must be manually deleted on devices where the option "This is a public computer" was used prior to log in or a log out with the request to delete local data with the affected versions has happened before.
Published: 2025-05-22T17:20:26.910Z
Updated: 2025-05-22T17:59:44.874Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-48061 |
vulnerable | 2026-06-08 07:27:15.431811 |
wire-webapp Has Insufficient Session Invalidation after User Logout
MEDIUM (5.6)
wire-webapp is the web application for the open-source messaging service Wire. A change caused a regression resulting in sessions not being properly invalidated. A user that logged out of the Wire webapp, could have been automatically logged in again after re-opening the application. This does not happen when the user is logged in as a temporary user by selecting "This is a public computer" during login or the user selects "Delete all your personal information and conversations on this device" upon logout. The underlying issue has been fixed with wire-webapp version 2025-05-20-production.0. As a workaround, this behavior can be prevented by either deleting all information upon logout as well as logging in as a temporary client.
Published: 2025-05-22T17:04:42.918Z
Updated: 2025-05-22T17:32:16.333Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-39380 |
vulnerable | 2026-06-08 05:47:18.697038 |
wire-webapp contains Improper Handling of Exceptional Conditions leading to a DoS via Markdown Rendering
MEDIUM (5.3)
Wire web-app is part of Wire communications. Versions prior to 2022-11-02 are subject to Improper Handling of Exceptional Conditions. In the wire-webapp, certain combinations of Markdown formatting can trigger an unhandled error in the conversion to HTML representation. The error makes it impossible to display the affected chat history, other conversations are not affected. The issue has been fixed in version 2022-11-02 and is already deployed on all Wire managed services. On-premise instances of wire-webapp need to be updated to docker tag 2022-11-02-production.0-v0.31.9-0-337e400 or wire-server 2022-11-03 (chart/4.26.0), so that their applications are no longer affected. As a workaround, you may use an iOS or Android client and delete the corresponding message from the history OR write 30 or more messages into the affected conversation to prevent the client from further rendering of the corresponding message. When attempting to retrieve messages from the conversation history, the error will continue to occur once the malformed message is part of the result.
Published: 2023-01-27T20:43:12.581Z
Updated: 2025-03-10T21:18:20.283Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-29168 |
vulnerable | 2026-06-08 05:42:47.045520 |
Cross Site Scripting in Wire Messages
CRITICAL (9.6)
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.
Published: 2022-06-25T07:05:09.000Z
Updated: 2025-04-23T18:08:54.718Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-24799 |
vulnerable | 2026-06-08 05:41:01.667737 |
Cross Site Scripting in Wire Webapp
CRITICAL (9.6)
wire-webapp is the web application interface for the wire messaging service. Insufficient escaping in markdown “code highlighting” in the wire-webapp resulted in the possibility of injecting and executing arbitrary HTML code and thus also JavaScript. If a user receives and views such a malicious message, arbitrary code is injected and executed in the context of the victim. This allows 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-03-30-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-03-30-production.0-v0.29.2-0-d144552 or wire-server 2022-03-30 (chart/4.8.0), so that their applications are no longer affected. There are no known workarounds for this issue. ### Patches * The issue has been fixed in wire-webapp **2022-03-30-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-03-30-production.0-v0.29.2-0-d144552** or wire-server **2022-03-30 (chart/4.8.0)**, so that their applications are no longer affected. ### Workarounds * No workarounds known ### For more information If you have any questions or comments about this advisory feel free to email us at [vulnerability-report@wire.com](mailto:vulnerability-report@wire.com) ### Credits We thank [Posix](https://twitter.com/po6ix) for reporting this vulnerability
Published: 2022-04-20T17:55:09.000Z
Updated: 2025-04-23T18:33:44.537Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-23605 |
vulnerable | 2026-06-08 05:40:57.819708 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-32683 |
vulnerable | 2026-06-08 05:32:07.831521 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-21400 |
vulnerable | 2026-06-08 05:29:11.822582 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.