VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

wiki: vulnerability history, versions and safety

wiki is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 72 releases, from Nov 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
4 vulnerabilities recorded H1 M1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

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 wiki vulnerabilities

Vulert verdict on wiki 0.13.0 i

Updated on 23 Oct 2026

Action needed: 0.13.0 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 71/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 0.13.0 — affected i
  • Vulnerabilities on record 4 over 4 years · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 1 packages i
  • Stars 1,940 i
  • OpenSSF scorecard 2/10 i
  • Last release 2 months ago i
  • Licence GPL-3.0 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 wiki, 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.13.0 31 Jul 2026 U1 GPL-3.0 Yes Details →
0.12.2 11 Oct 2025 U1 GPL-3.0 Yes Details →
0.12.1 16 Sep 2025 U1 GPL-3.0 Yes Details →
0.12.0 01 May 2025 U1 GPL-3.0 Yes Details →
0.11.2 21 Aug 2024 U1 GPL-3.0 Yes Details →
0.11.1 10 Apr 2024 U1 GPL-3.0 Yes Details →
0.11.0 21 Mar 2024 U1 GPL-3.0 Yes Details →
0.10.1 16 Mar 2024 U1 GPL-3.0 Yes Details →
0.10.0 15 May 2023 H1 U2 GPL-3.0 Yes Details →
0.10.0b1 25 Jan 2023 H1 U2 GPL-3.0 Yes Details →
0.9.0 27 Jun 2022 H1 U2 GPL-3.0 Yes Details →
0.8.2 07 May 2022 H1 U1 GPL-3.0 Yes Details →
0.8.1 25 Apr 2022 H1 U1 GPL-3.0 Yes Details →
0.8.0 14 Feb 2022 H1 U2 GPL-3.0 Yes Details →
0.7.10 29 Dec 2021 H1 U1 GPL-3.0 Yes Details →
0.7.9 16 Nov 2021 H1 U1 GPL-3.0 Yes Details →
0.7.8 25 Oct 2021 H1 M1 U2 GPL-3.0 Yes Details →
0.7.7 28 Aug 2021 H1 M1 U2 GPL-3.0 Yes Details →
0.7.6 01 Aug 2021 H1 M1 U2 GPL-3.0 Yes Details →
0.7.5 10 Apr 2021 H1 M1 U2 GPL-3.0 Yes Details →
0.7.4 10 Apr 2021 H1 M1 U2 GPL-3.0 Yes Details →
0.7.3 11 Jan 2021 H1 M1 U2 GPL-3.0 Yes Details →
0.7.2 08 Jan 2021 H1 M1 U2 GPL-3.0 Yes Details →
0.7.1 28 Dec 2020 H1 M1 U2 GPL-3.0 Yes Details →
0.7.0 28 Oct 2020 H1 M1 U2 GPL-3.0 Yes Details →
0.6.0 03 Jun 2020 H1 M1 U2 GPL-3.0 Yes Details →
0.6.0b2 15 Apr 2020 H1 M1 U2 GPL-3.0 Yes Details →
0.6.0b1 15 Feb 2020 H1 M1 U2 GPL-3.0 Yes Details →
0.5.0 19 Nov 2019 H1 M1 U2 GPL-3.0 Yes Details →
0.4.5 17 Jul 2019 H1 M1 U2 GPL-3.0 Yes Details →
0.4.4 01 Feb 2019 H1 M1 U2 GPL-3.0 Yes Details →
0.4.3 01 Feb 2019 H1 M1 U2 GPL-3.0 Yes Details →
0.4.2 25 Oct 2018 H1 M1 U2 GPL-3.0 Yes Details →
0.5.0.dev20181021091629 21 Oct 2018 H1 M1 U2 GPL-3.0 Yes Details →
0.4.1 20 Oct 2018 H1 M1 U2 GPL-3.0 Yes Details →
0.4.0b3 17 Sep 2018 H1 M1 U2 GPL-3.0 Yes Details →
0.4.0b2 15 Sep 2018 H1 M1 U2 GPL-3.0 Yes Details →
0.4.0b1 02 Aug 2018 H1 M1 U2 GPL-3.0 Yes Details →
0.4.0a5 18 Jul 2018 H1 M1 U2 GPL-3.0 Yes Details →
0.4.0a4 30 Mar 2018 H1 M1 U2 GPL-3.0 Yes Details →
0.4.0a3 28 Feb 2018 H1 M1 U2 GPL-3.0 Yes Details →
0.4.0a2 25 Feb 2018 H1 M1 U2 GPL-3.0 Yes Details →
0.4.0a1 20 Feb 2018 H1 M1 U2 GPL-3.0 Yes Details →
0.3.1 10 Feb 2018 H1 M1 U2 GPL-3.0 Yes Details →
0.3.0 29 Jan 2018 H1 M1 U2 GPL-3.0 Yes Details →
0.3.0rc1 29 Jan 2018 H1 M1 U2 GPL-3.0 Yes Details →
0.2.5 29 Jan 2018 H1 M1 U2 GPL-3.0 Yes Details →
0.3.0b4 15 Jan 2018 H1 M1 U2 GPL-3.0 Yes Details →
0.3.0b3 06 Sep 2017 H1 M1 U2 GPL-3.0 Yes Details →
0.3.0b2 16 Aug 2017 H1 M1 U2 GPL-3.0 Yes Details →
0.3.0b1 20 Jul 2017 H1 M1 U2 GPL-3.0 Yes Details →
0.2.4 21 Apr 2017 H1 M1 U2 GPL-3.0 Yes Details →
0.2.3 15 Apr 2017 H1 M1 U2 GPL-3.0 Yes Details →
0.2.2 15 Apr 2017 H1 M1 U2 GPL-3.0 Yes Details →
0.2.1 27 Feb 2017 H1 M1 U2 GPL-3.0 Yes Details →
0.2.0 28 Dec 2016 H1 M1 U2 GPL-3.0 Yes Details →
0.2.0b2 02 Nov 2016 H1 M1 U2 GPL-3.0 Yes Details →
0.2.0b1 12 Oct 2016 H1 M1 U2 GPL-3.0 Yes Details →
0.1.2 19 Jun 2016 H1 M1 U2 GPL-3.0 Yes Details →
0.1.1 05 May 2016 H1 M1 U2 GPL-3.0 Yes Details →
0.1.0 04 Feb 2016 H1 M1 U2 GPL-3.0 Yes Details →
0.1.0b0 19 Jan 2016 H1 M1 U2 GPL-3.0 Yes Details →
0.1.0.dev20160119155955 19 Jan 2016 H1 M1 U2 GPL-3.0 Yes Details →
0.0.24.4.post1 27 Dec 2015 H1 M1 U2 GPL-3.0 Yes Details →
0.0.24.4 26 Dec 2015 H1 M1 U2 GPL-3.0 Yes Details →
0.0.24.3 24 Sep 2015 H1 M1 U2 GPL-3.0 Yes Details →
0.0.24.2 05 Feb 2015 H1 M1 U2 GPL-3.0 Yes Details →
0.0.24.1 27 Jan 2015 H1 M1 U2 GPL-3.0 Yes Details →
0.0.23 06 Jan 2014 H1 M1 U2 GPL-3.0 Yes Details →
0.0.22 24 Nov 2013 H1 M1 U2 GPL-3.0 Yes Details →
0.0.21 18 Nov 2013 H1 M1 U2 GPL-3.0 Yes Details →
0.0.20 16 Jul 2013 H1 M1 U2 GPL-3.0 Yes Details →

All 72 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 2
  • 2024 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for wiki

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-28865: Denial of Service in django-wiki 7.5 high 0.10.1 18 Mar 2024
CVE-2024-28865: Denial of Service Vulnerability in django-wiki via Regular Expression Loop 7.5 high 0.10.1 07 Jul 2026
CVE-2021-25986: Cross-site Scripting in django-wiki 5.4 medium 0.7.9 02 Dec 2021
CVE-2021-25986: Stored Cross-Site Scripting (XSS) in Django-wiki N/A unrated 9eaccc7519e4206a4d2f22640882f0737b2da9c5 23 Nov 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 wiki

Is wiki safe to use?

Vulert records 4 vulnerabilities for wiki in PyPI: 0 critical, 1 high, 1 medium and 0 low, plus 2 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 wiki's Vulert package health score?

Vulert scores wiki 71/100, which reads as in good shape. 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 wiki affected?

Yes. 0.13.0, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of wiki should I use?

0.13.0 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 wiki have?

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

1 vulnerability was recorded for wiki in the last 12 months, and the oldest entry in this database dates to 23 Nov 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 wiki 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 wiki for upcoming vulnerabilities?

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