WeblateOrg weblate up to 5.10 Setting get request method with sensitive query strings
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in WeblateOrg weblate up to 5.10. This affects an unknown part of the component Setting Handler. Such manipulation leads to use of get request method with sensitive query strings. This vulnerability is uniquely identified as CVE-2025-32021. The attack can be launched remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in WeblateOrg weblate up to 5.10. Affected by this issue is some unknown functionality of the component Setting Handler. The manipulation with an unknown input leads to a use of get request method with sensitive query strings vulnerability. Using CWE to declare the problem leads to CWE-598. The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request. Impacted is confidentiality. CVE summarizes:
Weblate is a web based localization tool. Prior to version 5.11, 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 logs in plaintext. If using Weblate official Docker image, nginx logs the URL and the token in plaintext. This issue is patched in version 5.11.
The advisory is available at github.com. This vulnerability is handled as CVE-2025-32021 since 04/01/2025. The exploitation is known to be difficult. The attack may be launched remotely. Additional levels of successful authentication are required for exploitation. The technical details are unknown and an exploit is not available.
Upgrading to version 5.11 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.2VulDB Meta Temp Score: 2.2
VulDB Base Score: 2.2
VulDB Temp Score: 2.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 2.2
CNA Vector (GitHub_M): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Use of get request method with sensitive query stringsCWE: CWE-598
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: weblate 5.11
Timeline
04/01/2025 🔍04/15/2025 🔍
04/15/2025 🔍
04/15/2025 🔍
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2025-32021 (🔍)
GCVE (CVE): GCVE-0-2025-32021
GCVE (VulDB): GCVE-100-304922
Entry
Created: 04/15/2025 23:15Changes: 04/15/2025 23:15 (63)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.