Threats affecting pkg:github/weblateorg/wlc

CVE-2026-62364 is a vulnerability in WeblateOrg's wlc command-line client prior to version 2.0.1. The issue involves exposure of an unscoped API token when wlc automatically discovers configuration files and uses the token without a matching URL. This can cause the token to be sent to an attacker-controlled URL if wlc runs in an untrusted repository or directory. The vulnerability is fixed in version 2.0.1.

CVE-2026-42150 is a cross-site scripting (XSS) vulnerability in the Weblate command-line client (wlc) prior to version 2.0.0. The vulnerability arises because the HTML output format embeds API response data into HTML without proper escaping, which can lead to XSS when the output is viewed in a browser. This issue has been addressed in version 2.0.0 of wlc. The vulnerability has a medium severity with a CVSS score of 5.1.

CVE-2026-23535 is a high-severity path traversal vulnerability in the Weblate command-line client (wlc) versions prior to 1.17.2. It allows a malicious Weblate server to instruct the client to write files to arbitrary locations on the user's filesystem during multi-translation downloads. Exploitation requires network access to a malicious or compromised Weblate server and user interaction to trigger the download. The vulnerability impacts confidentiality, integrity, and availability by enabling unauthorized file writes, potentially leading to code execution or system compromise. The issue is fixed in wlc version 1.17.2. European organizations using vulnerable wlc versions should upgrade promptly and validate server trustworthiness.

wlc is a Weblate command-line client using Weblate's REST API. Prior to 1.17.0, wlc supported providing unscoped API keys in the setting. This practice was discouraged for years, but the code was never removed. This might cause the API key to be leaked to different servers.

wlc is a Weblate command-line client using Weblate's REST API. Prior to 1.17.0, the SSL verification would be skipped for some crafted URLs. This vulnerability is fixed in 1.17.0.