CVE-2025-32021: VCS credentials included in URL parameters are potentially logged and saved into browser history as plaintext
Summary When creating a new component from an existing component that has a source code repository URL specified in settings, this URL is included in the client's URL parameters during the creation process. If, for example, the source code repository URL contains GitHub credentials, the confidential PAT and username are shown in plaintext and get saved into browser history.
Published Apr 15, 2025
Affected packages
weblate
- Ecosystem
- PyPI
- Affected
- < 5.11
- Fixed in
- 5.11
- Check
pip show weblate
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
When creating a new component from an existing component that has a source code repository URL specified in settings, this URL is included in the client's URL parameters during the creation process. If, for example, the source code repository URL contains GitHub credentials, the confidential PAT and username are shown in plaintext and get saved into browser history. Moreover, if the request URL is logged, the credentials are written to the logs in plaintext.
The problematic URL in question is of this form:
https://<HOST>/create/component/vcs/?repo=https%3A%2F%2F<GITHUB USERNAME>%3A<GITHUB PAT>%40github.com%2F<REPOSITORY OWNER>%2F<REPOSITORY NAME>.git&project=1&category=&name=<REDACTED>&slug=<REDACTED>&is_glossary=False&vcs=github&source_language=228&license=&source_component=1#existingIf using Weblate official Docker image, nginx logs the URL and the token in plaintext:
nginx stdout | 127.0.0.1 - - [04/Apr/2025:10:46:54 +0000] "GET /create/component/vcs/?repo=https%3A%2F%2F<GITHUB USERNAME>%3A<GITHUB PAT>%40github.com%2F<REPOSITORY OWNER>%2F<REPOSITORY NAME>.git&project=1&category=&name=<REDACTED>&slug=<REDACTED>&is_glossary=False&vcs=github&source_language=228&license=&source_component=1 HTTP/1.1" 200 17625 "<REDACTED>" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:136.0) Gecko/20100101 Firefox/136.0"Reproduction
- In a project, create a component which has the _Repository push URL_ setting configured with, for example, a GitHub repository URL including a username and a PAT.
- In the same project, create another component using the _From existing component_ option and selecting the previous component as the source. Click _Continue_.
- Observe that the URL parameter
repoincludes the secret PAT configured in the original components settings. The URL with the token is potentially saved as plaintext in browser history and server logs. - Select a translation file to import and click _Continue_.
- Observe again the same
repoparameter in the URL.
Impact
- If server logs are compromised, the attacker may be able to gain access to private repositories potentially containing sensitive source code.
- Under common browser settings, the URL containing VCS credentials is saved into browser history. Browser extensions, for example, are often able to read the history and thus offer a realistic attack vector to gain access to the credentials.
Credited to joonashak, nijel, gersona.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-55227
Private Weblate projects vulnerable to observable object existence disclosure via globally scoped object lookups
medium4.3Aug 28, 2026CVE-2026-50127
Weblate SSRF: outbound URL guard misses some private ranges
medium5.9Jul 7, 2026CVE-2026-45106
Weblate: Stored HTML injection in editor search preview
medium4.6May 15, 2026CVE-2026-44263
Weblate Vulnerable to Private Translation Enumeration via Screenshot API
medium4.3May 7, 2026CVE-2026-44264
Weblate vulnerable to XSS via crafted Markdown
medium4.3May 7, 2026CVE-2026-41519
Weblate Doesn't Invalidate API Token on Password Change
medium4.2Apr 30, 2026
