Vulnerabilities in pkg:pypi/wlc

PACKAGE
Advisory Identifier: GHSA-3mqq-hv9c-85hc
Share
Advisory Summary

CVE-2026-62364 is a LOW (CVSS 2.3) wlc may disclose api tokens vulnerability (CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data) affecting Wlc libraries in the PyPI ecosystem. The issue involves wlc may disclose api tokens to project-configured urls. Remediation is available by upgrading affected packages to version 2.0.1.

5 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:pypi/wlc

5 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:pypi/wlc. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-3mqq-hv9c-85hc CVE-2026-62364 LOW wlc may disclose API tokens to project-configured URLs
GHSA-gx2m-mcc2-r4p3 CVE-2026-42150 MODERATE wlc: print_html outputs API data without HTML escaping
GHSA-mmwx-79f6-67jg CVE-2026-23535 HIGH Weblate wlc path traversal vulnerability: Unsanitized API slugs in download command
GHSA-9rp8-h4g8-8766 CVE-2026-22251 MODERATE Weblate wlc has insecure API key configuration
GHSA-2mmv-7rrp-g8xh CVE-2026-22250 LOW Weblate command-line client susceptible to SSL verification skip

CVE-2026-62364 at a Glance

CVE Identifier CVE-2026-62364
GHSA Identifier GHSA-3mqq-hv9c-85hc
Severity LOW
CVSS v3.1 Base Score 2.3
CWE Classification CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data
Affected Product Wlc
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 2.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N).

Attack Vector Local (AV:L)
Attack Complexity High (AC:H)
Privileges Required High (PR:H)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-62364

To remediate this vulnerability, upgrade all affected Wlc dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

wlc fixed: 2.0.1 
pip install wlc>=2.0.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

pip show wlc

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-62364, inspect your installed packages using pip:

pip show wlc

Analyze the terminal output to locate any version of Wlc in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.0.1), your application is affected.

Note: The pip show wlc command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data, where the product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted. In Wlc, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact wlc could send an unscoped API token to an unintended server when run inside a directory tree containing attacker-controlled project configuration. If `.weblate`, `.weblate.ini`, or `weblate.ini` defines an API url, and the user supplies a token with `WLC_KEY` or `--key` without also pinning the URL, wlc would send the token to the project-configured URL. Impacted users are those running wlc in untrusted repositories, pull request checkouts, or directories with untrusted ancestor configuration while using `WLC_KEY` or `--key`. ### Patches The issue is patched in wlc 2.0.1 via https://github.com/WeblateOrg/wlc/pull/1500. The fix rejects unscoped keys when the API URL comes from automatically discovered project configuration: - `WLC_KEY` now requires `WLC_URL`. - `--key` now requires `--url`. - URL-scoped keys in the `[keys]` configuration section remain supported. Users should upgrade to wlc 2.0.1 or newer. ### Workarounds Without upgrading, users can avoid the issue by explicitly pinning the API URL whenever using an unscoped key: `WLC_URL=https://hosted.weblate.org/api/ WLC_KEY=... wlc ...` or: `wlc --url https://hosted.weblate.org/api/ --key ... ...` Alternatively, use URL-scoped keys in the [keys] section instead of WLC_KEY or --key, and avoid running wlc with secrets in untrusted checkouts. - The issue was independently reported by [type5afe](https://hackerone.com/type5afe) and [visionx7](https://hackerone.com/visionx7) using HackerOne.

CVE-2026-62364 Affected Wlc Versions

1 component(s)
Fixed Versions:
2.0.1
Product / Package Ecosystem Affected Versions Fixed Version
wlc
pypi/wlc
PyPI
< 2.0.1
2.0.1

References

GitHub Advisory / Wiki ADVISORY
https://github.com/WeblateOrg/wlc/security/advisories/GHSA-3mqq-hv9c-85hc
Wlc Source Repository REPOSITORY
https://github.com/WeblateOrg/wlc/pull/1500
Security Fix Commit FIX COMMIT
https://github.com/WeblateOrg/wlc/commit/15cbdfc5b2c6183ef6864ea758091643a0ce6c89
Wlc Source Repository REPOSITORY
https://github.com/WeblateOrg/wlc
Wlc Release RELEASE
https://github.com/WeblateOrg/wlc/releases/tag/2.0.1

Frequently Asked Questions

What is CVE-2026-62364?
CVE-2026-62364 is a security vulnerability in Wlc involving wlc may disclose API tokens to project-configured URLs under CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data.
Which Wlc versions are affected?
Affected versions include releases prior to 2.0.1 across affected packages: wlc.
What version fixes CVE-2026-62364?
Upgrading to 2.0.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is wlc affected?
Yes, wlc is affected in releases prior to 2.0.1. Upgrade your dependency to 2.0.1 or later.
What is the CVSS score of CVE-2026-62364?
CVE-2026-62364 has a CVSS v3.1 base score of 2.3 (LOW) with vector string CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N.
What CWE is associated with CVE-2026-62364?
CVE-2026-62364 is classified under CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data (The product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted.).
How can I check PyPI dependencies for CVE-2026-62364?
Run the dependency tree command: 'pip show wlc'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-3mqq-hv9c-85hc",
  "modified" : "2026-09-22T20:34:07Z",
  "published" : "2026-09-22T20:34:07Z",
  "aliases" : [ "CVE-2026-62364" ],
  "summary" : "wlc may disclose API tokens to project-configured URLs",
  "details" : "### Impact\n\nwlc could send an unscoped API token to an unintended server when run inside a directory tree containing attacker-controlled project configuration.\n\nIf `.weblate`, `.weblate.ini`, or `weblate.ini` defines an API url, and the user supplies a token with `WLC_KEY` or `--key` without also pinning the URL, wlc would send the token to the project-configured URL.\n\nImpacted users are those running wlc in untrusted repositories, pull request checkouts, or directories with untrusted ancestor configuration while using `WLC_KEY` or `--key`.\n\n### Patches\n\nThe issue is patched in wlc 2.0.1 via https://github.com/WeblateOrg/wlc/pull/1500.\n\nThe fix rejects unscoped keys when the API URL comes from automatically discovered project configuration:\n\n- `WLC_KEY` now requires `WLC_URL`.\n- `--key` now requires `--url`.\n- URL-scoped keys in the `[keys]` configuration section remain supported.\n\nUsers should upgrade to wlc 2.0.1 or newer.\n\n### Workarounds\n\nWithout upgrading, users can avoid the issue by explicitly pinning the API URL whenever using an unscoped key:\n\n`WLC_URL=https://hosted.weblate.org/api/ WLC_KEY=... wlc ...`\n\nor:\n\n`wlc --url https://hosted.weblate.org/api/ --key ... ...`\n\nAlternatively, use URL-scoped keys in the [keys] section instead of WLC_KEY or --key, and avoid running wlc with secrets in untrusted checkouts.\n\n- The issue was independently reported by [type5afe](https://hackerone.com/type5afe) and [visionx7](https://hackerone.com/visionx7) using HackerOne.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "wlc"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.0.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/WeblateOrg/wlc/security/advisories/GHSA-3mqq-hv9c-85hc"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/WeblateOrg/wlc/pull/1500"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/WeblateOrg/wlc/commit/15cbdfc5b2c6183ef6864ea758091643a0ce6c89"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/WeblateOrg/wlc"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/WeblateOrg/wlc/releases/tag/2.0.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-349" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-22T20:34:07Z",
    "nvd_published_at" : null
  }
}