CVE-2019-13177: verification.py in django-rest-registration (aka Django REST Registration library) before 0.5.0 relies on a st

Q: How do I fix CVE-2019-13177?

django-rest-registration: upgrade to 0.5.0. Exact commands for each OS are on this page.

Q: Is CVE-2019-13177 being exploited?

CVE-2019-13177 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-2019-13177 affect?

CVE-2019-13177 affects django-rest-registration. Severity is critical (CVSS 9.8). verification.py in django-rest-registration (aka Django REST Registration library) before 0.5.0 relies on a static string for signatures (i.e., the Django Signing API is misused), which allows remote attackers to spoof the verification proc

Q: How urgent is CVE-2019-13177?

Priority 63/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2019-13177 is a critical-severity flaw (CVSS 9.8) affecting django-rest-registration. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

verification.py in django-rest-registration (aka Django REST Registration library) before 0.5.0 relies on a static string for signatures (i.e., the Django Signing API is misused), which allows remote attackers to spoof the verification process. This occurs because incorrect code refactoring led to calling a security-critical function with an incorrect argument.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.6% (top 24%)
CISA exploited list	No
Weakness	CWE-347
Published	2019-07-02
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: django-rest-registration project

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

Am I affected?

Timeline

2019-07-02 22:15 UTCPublished CVE record published
2026-06-17 02:16 UTCUpdated Record last modified

django-rest-registration project django-rest-registration UPGRADE

Affected: > 0.1.0 and < 0.5.0

Fixed in: 0.5.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy django-rest-registration || rpm -q django-rest-registration || django-rest-registration --version

2. UPGRADE to 0.5.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade django-rest-registration

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade django-rest-registration

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-2019-13177?

django-rest-registration: upgrade to 0.5.0. Exact commands for each OS are on this page.

Is CVE-2019-13177 being exploited?

CVE-2019-13177 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-2019-13177 affect?

CVE-2019-13177 affects django-rest-registration. Severity is critical (CVSS 9.8). verification.py in django-rest-registration (aka Django REST Registration library) before 0.5.0 relies on a static string for signatures (i.e., the Django Signing API is misused), which allows remote attackers to spoof the verification proc

How urgent is CVE-2019-13177?

Priority 63/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Django vulnerabilities

References

← Back to latest CVEs