VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

coderedcms: vulnerability history, versions and safety

coderedcms is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 38 releases, first recorded in Oct 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all coderedcms vulnerabilities

Vulert verdict on coderedcms 6.0.0 i

Updated on 22 Oct 2026

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

Package health score 67/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

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

  • Current release 6.0.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 22 Oct 2023 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 3 packages i
  • Stars 761 i
  • OpenSSF scorecard 1/10 i
  • Last release 13 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 coderedcms, 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
6.0.0 12 Sep 2025 none non-standard — Details →
5.0.2 03 Sep 2025 none non-standard — Details →
5.0.1 09 May 2025 none non-standard — Details →
5.0.0 01 Mar 2025 none non-standard — Details →
5.0.0b1 13 Feb 2025 none non-standard — Details →
4.1.1 10 Feb 2025 none non-standard — Details →
4.1.0 14 Nov 2024 none non-standard — Details →
4.0.1 16 Jul 2024 none non-standard — Details →
4.0.0 30 May 2024 none non-standard — Details →
3.0.4 18 May 2024 none non-standard — Details →
3.0.3 11 Jan 2024 none non-standard — Details →
3.0.2 27 Nov 2023 none non-standard — Details →
3.0.1 21 Nov 2023 none non-standard — Details →
3.0.0 13 Nov 2023 none non-standard — Details →
2.1.4 20 Jul 2023 none non-standard — Details →
2.1.3 12 Jul 2023 none non-standard — Details →
2.1.2 10 May 2023 none non-standard — Details →
2.1.1 21 Apr 2023 none non-standard — Details →
2.1.0 21 Apr 2023 none non-standard — Details →
2.0.0 27 Feb 2023 none non-standard — Details →
1.0.3 21 Feb 2023 none non-standard — Details →
1.0.2 17 Feb 2023 none non-standard — Details →
1.0.1 25 Aug 2022 none non-standard — Details →
1.0.0 23 Aug 2022 none non-standard — Details →
1.0.0rc3 11 Aug 2022 none non-standard — Details →
1.0.0rc2 11 Aug 2022 none non-standard — Details →
1.0.0rc1 11 Aug 2022 none non-standard — Details →
0.25.2 29 Jul 2022 none non-standard — Details →
0.25.1 20 Jul 2022 none non-standard — Details →
0.25.0 14 Jul 2022 none non-standard — Details →
0.24.1 22 Jun 2022 none non-standard — Details →
0.24.0 10 Jun 2022 none non-standard — Details →
0.23.1 03 Jun 2022 none non-standard — Details →
0.23.0 13 May 2022 none non-standard — Details →
0.22.3 29 Sep 2021 none non-standard — Details →
0.22.2 23 Sep 2021 M1 U1 non-standard Yes Details →
0.22.1 14 Sep 2021 M1 U1 non-standard Yes Details →
0.22.0 10 Sep 2021 M1 U1 non-standard Yes Details →
0.21.1 15 Aug 2021 M1 U1 non-standard Yes Details →
0.21.0 03 Aug 2021 M1 U1 non-standard Yes Details →
0.20.0 25 Jan 2021 M1 U1 non-standard Yes Details →
0.19.1 15 Dec 2020 M1 U1 non-standard Yes Details →
0.19.0 08 Aug 2020 M1 U1 non-standard Yes Details →
0.19.0rc1 05 Aug 2020 M1 U1 non-standard Yes Details →
0.18.2 22 May 2020 M1 U1 non-standard Yes Details →
0.18.1 21 May 2020 M1 U1 non-standard Yes Details →
0.18.0 11 Apr 2020 M1 U1 non-standard Yes Details →
0.17.0 13 Jan 2020 M1 U1 non-standard Yes Details →
0.16.3 01 Oct 2019 M1 U1 non-standard Yes Details →
0.16.2 13 Aug 2019 M1 U1 non-standard Yes Details →
0.16.1 12 Aug 2019 M1 U1 non-standard Yes Details →
0.16.0 12 Aug 2019 M1 U1 non-standard Yes Details →
0.15.2 15 Jul 2019 M1 U1 non-standard Yes Details →
0.15.1 15 Jul 2019 M1 U1 non-standard Yes Details →
0.15.0 04 Jun 2019 M1 U1 non-standard Yes Details →
0.14.1 04 May 2019 M1 U1 non-standard Yes Details →
0.14.0 17 Apr 2019 M1 U1 non-standard Yes Details →
0.13.3 10 Apr 2019 M1 U1 non-standard Yes Details →
0.13.2 04 Apr 2019 M1 U1 non-standard Yes Details →
0.13.1 01 Apr 2019 M1 U1 non-standard Yes Details →
0.13.0 26 Mar 2019 M1 U1 non-standard Yes Details →
0.12.1 13 Feb 2019 M1 U1 non-standard Yes Details →
0.12.0 13 Feb 2019 M1 U1 non-standard Yes Details →
0.11.0 23 Jan 2019 M1 U1 non-standard Yes Details →
0.10.0 17 Dec 2018 M1 U1 non-standard Yes Details →
0.9.1 10 Dec 2018 M1 U1 non-standard Yes Details →
0.9.0 03 Dec 2018 M1 U1 non-standard Yes Details →
0.8.0 18 Oct 2018 M1 U1 non-standard Yes Details →
0.7.1 14 Sep 2018 M1 U1 non-standard Yes Details →
0.7.0 12 Sep 2018 M1 U1 non-standard Yes Details →
0.6.0 30 Aug 2018 M1 U1 non-standard Yes Details →
0.5.1 01 Aug 2018 M1 U1 non-standard Yes Details →
0.5.0 31 Jul 2018 M1 U1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 2

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

03 Vulnerabilities

Recorded vulnerabilities for coderedcms

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Path Traversal Vulnerability in Wagtail CRX CodeRed Extensions 6.5 medium 0.22.3 22 Oct 2023
Path Traversal Vulnerability in Wagtail CRX CodeRed Extensions N/A unrated 0.22.3 22 Oct 2023

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 coderedcms

Is coderedcms safe to use?

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

Vulert scores coderedcms 67/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 coderedcms affected?

No. 6.0.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.

Which version of coderedcms should I use?

6.0.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 coderedcms have?

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

0 vulnerabilities were recorded for coderedcms in the last 12 months, and the oldest entry in this database dates to 22 Oct 2023. 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 coderedcms 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 coderedcms for upcoming vulnerabilities?

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