This page lists publicly disclosed CVE vulnerabilities affecting weblate wlc (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2026-42150 | wlc is a Weblate command-line client using Weblate's REST API. Prior to version 2.0.0, the HTML output format in wlc embeds API response data into HTML without escaping, allowing cross-site scripting when the output is rendered in a browser. This issue has been patched in version 2.0.0. | [email protected] | 5.1 | 0.03% | 2026-05-08 | 2026-05-12 |
| CVE-2026-23535 | wlc is a Weblate command-line client using Weblate's REST API. Prior to 1.17.2, the multi-translation download could write to an arbitrary location when instructed by a crafted server. This vulnerability is fixed in 1.17.2. | [email protected] | 8.0 | 0.03% | 2026-01-16 | 2026-02-18 |
| CVE-2026-22251 | 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. | [email protected] | 5.3 | 0.01% | 2026-01-12 | 2026-01-27 |
| CVE-2026-22250 | 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. | [email protected] | 2.5 | 0.01% | 2026-01-12 | 2026-01-27 |