CVE-2022-4589: A vulnerability has been found in cyface Terms and Conditions Module up to 2.0.9 and classified as problematic

Q: How do I fix CVE-2022-4589?

django terms and conditions: upgrade to 2.0.10. Exact commands for each OS are on this page.

Q: Is CVE-2022-4589 being exploited?

CVE-2022-4589 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-4589 affect?

CVE-2022-4589 affects django terms and conditions. Severity is medium (CVSS 5.5). A vulnerability has been found in cyface Terms and Conditions Module up to 2.0.9 and classified as problematic. Affected by this vulnerability is the function returnTo of the file termsandconditions/views.py. The manipulation leads to open

Q: How urgent is CVE-2022-4589?

Priority 30/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

CVE-2022-4589 is a medium-severity flaw (CVSS 5.5) affecting django terms and conditions. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability has been found in cyface Terms and Conditions Module up to 2.0.9 and classified as problematic. Affected by this vulnerability is the function returnTo of the file termsandconditions/views.py. The manipulation leads to open redirect. The attack can be launched remotely. Upgrading to version 2.0.10 is able to address this issue. The name of the patch is 03396a1c2e0af95e12a45c5faef7e47a4b513e1a. It is recommended to upgrade the affe

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.5% (top 58%)
CISA exploited list	No
Weakness	CWE-601
Published	2022-12-17
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: django terms and conditions project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-12-17 13:15 UTCPublished CVE record published
2026-06-17 05:21 UTCUpdated Record last modified

django terms and conditions project django terms and conditions UPGRADE

Affected: < 2.0.10

Fixed in: 2.0.10

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy django-terms-and-conditions || rpm -q django-terms-and-conditions || django-terms-and-conditions --version

2. UPGRADE to 2.0.10 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade django-terms-and-conditions

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade django-terms-and-conditions

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-4589?

django terms and conditions: upgrade to 2.0.10. Exact commands for each OS are on this page.

Is CVE-2022-4589 being exploited?

CVE-2022-4589 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-4589 affect?

CVE-2022-4589 affects django terms and conditions. Severity is medium (CVSS 5.5). A vulnerability has been found in cyface Terms and Conditions Module up to 2.0.9 and classified as problematic. Affected by this vulnerability is the function returnTo of the file termsandconditions/views.py. The manipulation leads to open

How urgent is CVE-2022-4589?

Priority 30/100. No elevated risk signals yet.

Software pages

Django vulnerabilities

References

← Back to latest CVEs