Skip to main content
No exploitation reportedFix available

CVE-2019-13177

No exploitation reported by the sources we read.

  • Published2019-07-02
  • Fixed in0.5.0
  • WeaknessCWE-347

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2019-07-0222:15CVE publishedNVD

Versions per branch

NVD · OSV
Django-rest-registration project django-rest-registration
BranchAffectedFixed in
0.x> 0.1.0, < 0.5.00.5.0
0.5< 0.5.00.5.0
0.x≥ 0.2.0, < 0.5.00.5.0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Django-rest-registration project django-rest-registration to 0.5.0

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVSS 3.09.8read 2026-10-23
  • NVDCVSS 2.07.5read 2026-10-23
  • NVDweakness (CWE)CWE-347read 2026-10-23
  • FIRST EPSSEPSS score1.6 %2026-11-08
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryCRITICAL2020-06-16

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2019-07-02
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-p3w6-jcg4-52xh

Frequently asked questions

What is CVE-2019-13177?

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.

Is CVE-2019-13177 actively exploited?

Active exploitation of CVE-2019-13177 has not been confirmed. Its EPSS score was 1.6% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2019-13177?

CVE-2019-13177 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running django-rest-registration? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record