VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

lin-cms: vulnerability history, versions and safety

lin-cms is a package in the PyPI ecosystem. Vulert records 8 vulnerabilities for it across 38 releases, from Aug 2021 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded C1 M3 U4
i
8 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all lin-cms vulnerabilities

Vulert verdict on lin-cms 0.4.11 i

Updated on 23 Oct 2026

Careful: 0.4.11 has 8 known vulnerabilities, and 8 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.4.11 — affected i
  • Vulnerabilities on record 8 over 4 years · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 8 i
  • Last release 39 months ago i
  • Licence MIT 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 lin-cms, 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
0.4.11 02 Jul 2023 C1 M3 U4 MIT No Details →
0.4.10 10 Feb 2023 U3 MIT No Details →
0.4.9 19 Jul 2022 U3 MIT No Details →
0.4.8 16 Mar 2022 U3 MIT No Details →
0.4.7 08 Mar 2022 U3 MIT No Details →
0.4.6 07 Mar 2022 U3 MIT No Details →
0.4.5 28 Jan 2022 U3 MIT No Details →
0.4.4 24 Jan 2022 U3 MIT No Details →
0.4.3 20 Jan 2022 U3 MIT No Details →
0.4.2 14 Jan 2022 U3 MIT No Details →
0.4.0 06 Jan 2022 U3 MIT No Details →
0.3.1 18 May 2021 U3 MIT No Details →
0.3.0a10 27 Jan 2021 U3 MIT No Details →
0.3.0a9 17 Jan 2021 U3 MIT No Details →
0.3.0a8 25 Dec 2020 U3 MIT No Details →
0.3.0a7 21 Dec 2020 U3 MIT No Details →
0.3.0a6 14 Dec 2020 U3 MIT No Details →
0.3.0a5 13 Dec 2020 U3 MIT No Details →
0.3.0a4 06 Dec 2020 U3 MIT No Details →
0.3.0a3 05 Dec 2020 U3 MIT No Details →
0.3.0a2 01 Dec 2020 U3 MIT No Details →
0.2.0b3 04 Mar 2020 M2 U4 MIT No Details →
0.2.0b2 14 Oct 2019 M2 U4 MIT No Details →
0.2.0b1 18 Jul 2019 M2 U4 MIT No Details →
0.1.1b4 17 Jun 2019 M2 U4 MIT No Details →
0.1.1b3 03 Jun 2019 M2 U4 MIT No Details →
0.1.1b2 07 May 2019 M3 U4 MIT No Details →
0.1.1b1 05 May 2019 M3 U4 MIT No Details →
0.1.1a8 02 May 2019 M3 U4 MIT No Details →
0.1.1a7 27 Apr 2019 M3 U4 MIT No Details →
0.1.1a6 26 Mar 2019 M3 U4 MIT No Details →
0.1.1a5 18 Mar 2019 M3 U4 MIT No Details →
0.1.1a4 10 Mar 2019 M3 U4 MIT No Details →
0.1.1a3 30 Jan 2019 M3 U4 MIT No Details →
0.1.1a2 26 Jan 2019 M3 U4 MIT No Details →
0.1.1a1 24 Jan 2019 M3 U4 MIT No Details →
0.3.0a3-py3.10 — C1 M3 U4 — No Details →
0.3.0a5-py3.10 — C1 M3 U4 — No 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

  • 2021 3
  • 2022 4
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for lin-cms

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-18698: Lin-CMS Flask Improper Authentication Vulnerability 9.8 critical No fix published 24 May 2022
CVE-2022-44244: Lin CMS Improper Authentication Vulnerability 6.6 medium No fix published 10 Nov 2022
CVE-2022-44244: Lin CMS Authentication Bypass Vulnerability 6.6 medium No fix published 07 Jul 2026
Lin-CMS-Flask Cross Site Scripting (XSS) Vulnerability in lin-cms 6.1 medium No fix published 24 May 2022
CVE-2020-18698: Improper Authentication in Lin-CMS-Flask v0.1.1 N/A unrated No fix published 16 Aug 2021

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 lin-cms

Is lin-cms safe to use?

Vulert records 8 vulnerabilities for lin-cms in PyPI: 1 critical, 0 high, 3 medium and 0 low, plus 4 not yet rated. 8 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is lin-cms's Vulert package health score?

Vulert scores lin-cms 50/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of lin-cms affected?

Yes. 0.4.11, the version you would install today, has 8 known vulnerabilities, and 8 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of lin-cms should I use?

0.4.11 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does lin-cms have?

8 vulnerabilities are recorded for lin-cms in the PyPI ecosystem: 1 critical, 0 high, 3 medium and 0 low, plus 4 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 lin-cms vulnerabilities disclosed?

1 vulnerability was recorded for lin-cms in the last 12 months, and the oldest entry in this database dates to 16 Aug 2021. 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 lin-cms 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 lin-cms for upcoming vulnerabilities?

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