WeblateOrg wlc up to 2.0.0 Configuration weblate.ini WLC_KEY/WLC_URL/--key input validation

Summaryinfo

A vulnerability was found in WeblateOrg wlc up to 2.0.0. It has been rated as problematic. The impacted element is an unknown function of the file weblate.ini of the component Configuration. Performing a manipulation of the argument WLC_KEY/WLC_URL/--key results in input validation. This vulnerability was named CVE-2026-62364. The attack needs to be approached locally. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in WeblateOrg wlc up to 2.0.0. It has been classified as problematic. This affects an unknown function of the file weblate.ini of the component Configuration. The manipulation of the argument WLC_KEY/WLC_URL/--key with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. This is going to have an impact on confidentiality. The summary by CVE is:

wlc is a Weblate command-line client using Weblate's REST API. Prior to 2.0.1, automatically discovered configuration from .weblate, .weblate.ini, or weblate.ini can select the API URL while an unscoped API token is supplied through WLC_KEY or --key without a matching WLC_URL or --url. When wlc runs in an untrusted repository, pull request checkout, or directory with untrusted ancestor configuration, it can send the token to an attacker-controlled project-configured URL. URL-scoped keys in [keys] are not affected. This issue is fixed in version 2.0.1.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-62364 since 07/14/2026. The exploitability is told to be easy. Attacking locally is a requirement. Additional levels of successful authentication are necessary for exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.

By approaching the search of inurl:weblate.ini it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 2.0.1 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-84823). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• WeblateOrg

Name

• wlc

Version

• 2.0

Website

• Product: https://github.com/WeblateOrg/wlc/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion