VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

wlc: vulnerability history, versions and safety

wlc is a package in the PyPI ecosystem. Vulert records 10 vulnerabilities for it across 31 releases, from Jan 2026 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded H1 M2 L2 U5
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
10 in the last 12 months

Most recent disclosure 01 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all wlc vulnerabilities

Vulert verdict on wlc 3.1.0 i

Updated on 23 Oct 2026

Good news: 3.1.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 10.

Package health score 53/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

What to do: Stay on 3.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.1.0 — unaffected i
  • Vulnerabilities on record 10 over 1 year · 10 in the last year i
  • Latest disclosure 01 Oct 2026 i
  • Highest CVSS 8.0 i
  • With no published fix 0 i
  • Stars 47 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence GPL-3.0-or-later i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for wlc, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.1.0 21 Oct 2026 none GPL-3.0-or-later — Details →
3.0.0 08 Oct 2026 none GPL-3.0-or-later — Details →
2.2.1 24 Sep 2026 none GPL-3.0-or-later — Details →
2.2.0 01 Sep 2026 none GPL-3.0-or-later — Details →
2.1.1 25 Jul 2026 none GPL-3.0-or-later — Details →
2.1.0 30 Jun 2026 none GPL-3.0-or-later — Details →
2.0.1 26 Jun 2026 none GPL-3.0-or-later — Details →
2.0.0 21 Apr 2026 L1 U1 GPL-3.0-or-later Yes Details →
1.17.2 16 Jan 2026 M1 L1 U2 GPL-3.0-or-later Yes Details →
1.17.1 13 Jan 2026 H1 M1 L1 U3 GPL-3.0-or-later Yes Details →
1.17.0 12 Jan 2026 H1 M1 L1 U3 GPL-3.0-or-later Yes Details →
1.16.1 10 Oct 2025 H1 M2 L2 U5 GPL-3.0-or-later Yes Details →
1.15.0 03 Sep 2024 H1 M2 L2 U5 GPL-3.0-or-later Yes Details →
1.14.0 23 Feb 2024 H1 M2 L2 U5 GPL-3.0-or-later Yes Details →
1.13.0 24 Mar 2022 H1 M2 L2 U5 GPL-3.0-or-later Yes Details →
1.12.0 19 May 2021 H1 M2 L2 U5 GPL-3.0-or-later Yes Details →
1.11.0 17 Mar 2021 H1 M2 L2 U5 GPL-3.0-or-later Yes Details →
1.10.0 11 Feb 2021 H1 M2 L2 U5 GPL-3.0-or-later Yes Details →
1.9.0 21 Dec 2020 H1 M2 L2 U5 GPL-3.0-or-later Yes Details →
1.8.0 11 Sep 2020 H1 M2 L2 U5 GPL-3.0-or-later Yes Details →
1.7.0 03 Sep 2020 H1 M2 L2 U5 GPL-3.0-or-later Yes Details →
1.6.0 01 Sep 2020 H1 M2 L2 U5 GPL-3.0-or-later Yes Details →
1.5.0 19 Jun 2020 H1 M2 L2 U5 non-standard Yes Details →
1.4.0 03 Jun 2020 H1 M2 L2 U5 non-standard Yes Details →
1.3.0 06 May 2020 H1 M2 L2 U5 non-standard Yes Details →
1.2.0 15 Oct 2019 H1 M2 L2 U5 non-standard Yes Details →
1.1.0 01 Feb 2019 H1 M2 L2 U5 non-standard Yes Details →
1.0.0 31 Jan 2019 H1 M2 L2 U5 non-standard Yes Details →
0.10.0 21 Oct 2018 H1 M2 L2 U5 non-standard Yes Details →
0.9.0 17 Oct 2018 H1 M2 L2 U5 non-standard Yes Details →
0.8.0 03 Mar 2017 H1 M2 L2 U5 non-standard Yes Details →
0.7.0 16 Dec 2016 H1 M2 L2 U5 non-standard Yes Details →
0.6.0 20 Sep 2016 H1 M2 L2 U5 non-standard Yes Details →
0.5.0 11 Jul 2016 H1 M2 L2 U5 non-standard Yes Details →
0.4.0 08 Jul 2016 H1 M2 L2 U5 non-standard Yes Details →
0.3.0 19 May 2016 H1 M2 L2 U5 non-standard Yes Details →
0.2.0 14 May 2016 H1 M2 L2 U5 non-standard Yes Details →
0.1.0 08 Apr 2016 H1 M2 L2 U5 non-standard Yes Details →

All 38 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 10

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 10 of the 10 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for wlc

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-23535: wlc Path Traversal Vulnerability in Weblate Allows Arbitrary File Write 8.0 high 1.17.2 16 Jan 2026
CVE-2026-23535: wlc Path Traversal Vulnerability in Weblate - Unsanitized API Slugs in Download Command 8.0 high 1.17.2 07 Jul 2026
Insecure API Key Configuration in wlc Package 5.3 medium 1.17.0 12 Jan 2026
CVE-2026-22251: wlc API Key Configuration Vulnerability 5.3 medium 1.17.0 07 Jul 2026
CVE-2026-42150: wlc Package Cross-Site Scripting Vulnerability Due to HTML Output 5.1 medium 2.0.0 24 Apr 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About wlc

Is wlc safe to use?

Vulert records 10 vulnerabilities for wlc in PyPI: 0 critical, 1 high, 2 medium and 2 low, plus 5 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is wlc's Vulert package health score?

Vulert scores wlc 53/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of wlc affected?

No. 3.1.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does wlc have?

10 vulnerabilities are recorded for wlc in the PyPI ecosystem: 0 critical, 1 high, 2 medium and 2 low, plus 5 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new wlc vulnerabilities disclosed?

10 vulnerabilities were recorded for wlc in the last 12 months, and the oldest entry in this database dates to 12 Jan 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of wlc are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor wlc for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the wlc version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.