{"id":"CVE-2021-21416","aliases":["DEBIAN-CVE-2021-21416","EUVD-2021-0057","GHSA-58c7-px5v-82hh","MGASA-2022-0178","PYSEC-2021-11","UBUNTU-CVE-2021-21416","openSUSE-SU-2021:0588-1","openSUSE-SU-2021:0597-1","openSUSE-SU-2024:11226-1","openSUSE-SU-2024:14138-1","openSUSE-SU-2026:12007-1"],"status":"published","title":"Potential sensitive information disclosed in error reports","description":"django-registration is a user registration package for Django. The django-registration package provides tools for implementing user-account registration flows in the Django web framework. In django-registration prior to 3.1.2, the base user-account registration view did not properly apply filters to sensitive data, with the result that sensitive data could be included in error reports rather than removed automatically by Django. Triggering this requires: A site is using django-registration \u003c 3.1.2, The site has detailed error reports (such as Django's emailed error reports to site staff/developers) enabled and a server-side error (HTTP 5xx) occurs during an attempt by a user to register an account. Under these conditions, recipients of the detailed error report will see all submitted data from the account-registration attempt, which may include the user's proposed credentials (such as a password).","severity":{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N","level":"low","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.0041,"percentile":0.35781,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-201","CWE-209"],"published":"2021-04-01T21:15:14Z","modified":"2026-10-23T18:03:24Z","fixes":[{"ecosystem":"PyPI","package":"django-registration","fixed_in":["3.1.2"],"sources":["ghsa","osv"]},{"ecosystem":"Debian:12","package":"python-django-registration","fixed_in":["3.3-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"python-django-registration","fixed_in":["3.3-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"python-django-registration","fixed_in":["3.3-1"],"sources":["osv"]},{"ecosystem":"Mageia:8","package":"python-django-registration","fixed_in":["3.2-2.mga8"],"sources":["osv"]},{"ecosystem":"openSUSE:Leap 15.2","package":"python-django-registration","fixed_in":["3.1.2-lp152.3.3.1"],"sources":["osv"]},{"ecosystem":"SUSE:Package Hub 15 SP2","package":"python-django-registration","fixed_in":["3.1.2-bp152.3.3.1"],"sources":["osv"]},{"ecosystem":"openSUSE:Tumbleweed","package":"python-django-registration","fixed_in":["3.3-2.2","5.2.1-1.3"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"PyPI","package":"django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.2"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"python-django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"python-django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"python-django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3-1"}]}]},{"source":"osv","ecosystem":"PyPI","package":"django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.2"}]}],"versions":["0.5","0.6","0.7","0.8","1.0","2.0","2.0.1","2.0.2","2.0.3","2.0.4","2.1","2.1.1","2.1.2","2.2","2.3","2.4","2.4.1","2.5","2.5.1","2.5.2","3.0","3.0.1","3.1","3.1.1"]},{"source":"osv","ecosystem":"Mageia:8","package":"python-django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2-2.mga8"}]}]},{"source":"osv","ecosystem":"PyPI","package":"django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.2"}]}],"versions":["0.5","0.6","0.7","0.8","1.0","2.0","2.0.1","2.0.2","2.0.3","2.0.4","2.1","2.1.1","2.1.2","2.2","2.3","2.4","2.4.1","2.5","2.5.1","2.5.2","3.0","3.0.1","3.1","3.1.1"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"python-django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.0+dfsg-2","2.0.4-1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"python-django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.2-1","2.2-2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"python-django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.2-2","2.2-3"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"python-django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.2-5"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"python-django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.3-1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"python-django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.3-1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"python-django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.3-1build1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"python-django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.3-1","3.3-1build1"]},{"source":"osv","ecosystem":"openSUSE:Leap 15.2","package":"python-django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.2-lp152.3.3.1"}]}]},{"source":"osv","ecosystem":"SUSE:Package Hub 15 SP2","package":"python-django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.2-bp152.3.3.1"}]}]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"python-django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3-2.2"}]}]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"python-django-registration","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.2.1-1.3"}]}]}],"products":[{"vendor":"django-registration_project","product":"django-registration"},{"vendor":"ubernostrum","product":"django-registration"}],"references":[{"url":"https://github.com/ubernostrum/django-registration/security/advisories/GHSA-58c7-px5v-82hh","tags":["x_refsource_CONFIRM","x_transferred","Mitigation","Third Party Advisory","advisory","web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-21416","tags":["advisory"]},{"url":"https://github.com/ubernostrum/django-registration/commit/2db0bb7ec35636ea46b07b146328b87b2cb13ca5","tags":["web"]},{"url":"https://github.com/pypa/advisory-database/tree/main/vulns/django-registration/PYSEC-2021-11.yaml","tags":["web"]},{"url":"https://github.com/advisories/GHSA-58c7-px5v-82hh"},{"url":"https://security-tracker.debian.org/tracker/CVE-2021-21416","tags":["advisory"]},{"url":"https://github.com/ubernostrum/django-registration","tags":["package"]},{"url":"https://advisories.mageia.org/MGASA-2022-0178.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=29052","tags":["report"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/2F72NF6ZBHDNQRLYZZFU7B52UQ4CZZRE/","tags":["web","advisory"]},{"url":"https://ubuntu.com/security/CVE-2021-21416","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-21416","tags":["report"]},{"url":"https://bugzilla.suse.com/1184427","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-21416","tags":["web"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/NL4XGVJ2AN5KEZDKGXRP3QKFGI24ETYA/","tags":["advisory"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2021-21416","title":"Potential sensitive information disclosed in error reports","description":"django-registration is a user registration package for Django. The django-registration package provides tools for implementing user-account registration flows in the Django web framework. In django-registration prior to 3.1.2, the base user-account registration view did not properly apply filters to sensitive data, with the result that sensitive data could be included in error reports rather than removed automatically by Django. Triggering this requires: A site is using django-registration \u003c 3.1.2, The site has detailed error reports (such as Django's emailed error reports to site staff/developers) enabled and a server-side error (HTTP 5xx) occurs during an attempt by a user to register an account. Under these conditions, recipients of the detailed error report will see all submitted data from the account-registration attempt, which may include the user's proposed credentials (such as a password).","status":"published","published":"2021-04-01T21:15:14Z","modified":"2024-08-03T18:09:16.086Z","cvss":[{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N","level":"low","assessor":"cna"}],"cwes":["CWE-209"],"updated_at":"2026-11-02T14:33:00.137099Z"}],"euvd":[{"id":"EUVD-2021-0057","description":"django-registration is a user registration package for Django. The django-registration package provides tools for implementing user-account registration flows in the Django web framework. In django-registration prior to 3.1.2, the base user-account registration view did not properly apply filters to sensitive data, with the result that sensitive data could be included in error reports rather than removed automatically by Django. Triggering this requires: A site is using django-registration \u003c 3.1.2, The site has detailed error reports (such as Django's emailed error reports to site staff/developers) enabled and a server-side error (HTTP 5xx) occurs during an attempt by a user to register an account. Under these conditions, recipients of the detailed error report will see all submitted data from the account-registration attempt, which may include the user's proposed credentials (such as a password).","status":"published","published":"2021-04-01T21:15:14Z","modified":"2024-08-03T18:09:16Z","cvss":[{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N","level":"low"}],"updated_at":"2026-11-03T03:25:06.347262Z"}],"ghsa":[{"id":"GHSA-58c7-px5v-82hh","title":"Potential sensitive information disclosed in error reports","description":"django-registration is a user-registration application for Django. \n\n### Impact\n\nThe django-registration package provides tools for implementing user-account registration flows in the Django web framework. In django-registration prior to 3.1.2, the base user-account registration view did not properly apply filters to sensitive data, with the result that sensitive data could be included in error reports rather than removed automatically by Django.\n\nTriggering this requires the following conditions:\n\n* A site is using django-registration \u003c 3.1.2\n* The site has detailed error reports (such as Django's [emailed error reports to site staff/developers](https://docs.djangoproject.com/en/3.1/howto/error-reporting/#email-reports)) enabled\n* A server-side error (HTTP 5xx) occurs during an attempt by a user to register an account\n\nUnder these conditions, recipients of the detailed error report will see all submitted data from the account-registration attempt, which may include the user's proposed credentials (such as a password).\n\n### Patches\n\nAs of version 3.1.2, django-registration properly applies Django's `sensitive_post_parameters()` decorator to the base user-registration view, which will cause all data from the HTTP request body to be filtered from detailed error reports in the event of a server-side crash during user account registration.\n\nNote that as applied, this filters *all* HTTP request data from error reports. To selectively allow some fields but not others, see Django's own documentation (in references) and the notes below for how to apply `sensitive_post_parameters()` manually to a particular codebase's `RegistrationView` subclass(es).\n\n### Workarounds\n\nUsers who cannot upgrade quickly can apply the `django.views.decorators.debug.sensitive_post_parameters()` decorator to their own registration views. The decorator should be applied on the `dispatch()` method of the appropriate `RegistrationView` class, using Django's `method_decorator()` helper. For example:\n\n```python\nfrom django.utils.decorators import method_decorator\nfrom django.views.decorators.debug import sensitive_post_parameters\n\nfrom django_registration.views import RegistrationView\n\nclass MyRegistrationView(RegistrationView):\n    \"\"\"\n    A RegistrationView subclass manually protected against sensitive information disclosure\n    in error reports.\n\n    \"\"\"\n    @method_decorator(sensitive_post_parameters())\n    def dispatch(self, *args, **kwargs):\n        return super().dispatch(*args, **kwargs)\n```\n\n### References\n\n* Django's documentation on [error reporting in production](https://docs.djangoproject.com/en/3.1/howto/error-reporting/)\n* [How Django's sensitive-data filters work](https://docs.djangoproject.com/en/3.1/howto/error-reporting/#filtering-error-reports)","status":"published","published":"2021-04-06T17:28:59Z","modified":"2024-09-16T21:29:06Z","cvss":[{"version":"4.0","score":2,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","level":"low"},{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N","level":"low"}],"cwes":["CWE-201","CWE-209"],"updated_at":"2026-11-02T14:38:02.773864Z"}],"nvd":[{"id":"CVE-2021-21416","description":"django-registration is a user registration package for Django. The django-registration package provides tools for implementing user-account registration flows in the Django web framework. In django-registration prior to 3.1.2, the base user-account registration view did not properly apply filters to sensitive data, with the result that sensitive data could be included in error reports rather than removed automatically by Django. Triggering this requires: A site is using django-registration \u003c 3.1.2, The site has detailed error reports (such as Django's emailed error reports to site staff/developers) enabled and a server-side error (HTTP 5xx) occurs during an attempt by a user to register an account. Under these conditions, recipients of the detailed error report will see all submitted data from the account-registration attempt, which may include the user's proposed credentials (such as a password).","status":"published","published":"2021-04-01T22:15:11.653Z","modified":"2026-06-17T03:35:31.983Z","cvss":[{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N","level":"low","assessor":"secondary"},{"version":"3.1","score":2.6,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N","level":"low","assessor":"primary"},{"version":"2.0","score":3.5,"vector":"AV:N/AC:M/Au:S/C:P/I:N/A:N","level":"low","assessor":"primary"}],"cwes":["CWE-209"],"updated_at":"2026-11-02T14:06:51.197859Z"}],"osv":[{"id":"CVE-2021-21416","description":"django-registration is a user registration package for Django. The django-registration package provides tools for implementing user-account registration flows in the Django web framework. In django-registration prior to 3.1.2, the base user-account registration view did not properly apply filters to sensitive data, with the result that sensitive data could be included in error reports rather than removed automatically by Django. Triggering this requires: A site is using django-registration \u003c 3.1.2, The site has detailed error reports (such as Django's emailed error reports to site staff/developers) enabled and a server-side error (HTTP 5xx) occurs during an attempt by a user to register an account. Under these conditions, recipients of the detailed error report will see all submitted data from the account-registration attempt, which may include the user's proposed credentials (such as a password).","status":"published","published":"2021-04-01T22:15:11.653Z","modified":"2026-10-20T10:54:29.011365793Z","cvss":[{"version":"3.1","score":2.6,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N","level":"low"}],"updated_at":"2026-11-02T15:44:18.004149Z"},{"id":"DEBIAN-CVE-2021-21416","description":"django-registration is a user registration package for Django. The django-registration package provides tools for implementing user-account registration flows in the Django web framework. In django-registration prior to 3.1.2, the base user-account registration view did not properly apply filters to sensitive data, with the result that sensitive data could be included in error reports rather than removed automatically by Django. Triggering this requires: A site is using django-registration \u003c 3.1.2, The site has detailed error reports (such as Django's emailed error reports to site staff/developers) enabled and a server-side error (HTTP 5xx) occurs during an attempt by a user to register an account. Under these conditions, recipients of the detailed error report will see all submitted data from the account-registration attempt, which may include the user's proposed credentials (such as a password).","status":"published","published":"2021-04-01T22:15:11.653Z","modified":"2026-10-23T18:03:24.968232745Z","cvss":[{"version":"3.1","score":2.6,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N","level":"low"}],"updated_at":"2026-11-02T15:45:34.637046Z"},{"id":"GHSA-58c7-px5v-82hh","title":"Potential sensitive information disclosed in error reports","description":"django-registration is a user-registration application for Django. \n\n### Impact\n\nThe django-registration package provides tools for implementing user-account registration flows in the Django web framework. In django-registration prior to 3.1.2, the base user-account registration view did not properly apply filters to sensitive data, with the result that sensitive data could be included in error reports rather than removed automatically by Django.\n\nTriggering this requires the following conditions:\n\n* A site is using django-registration \u003c 3.1.2\n* The site has detailed error reports (such as Django's [emailed error reports to site staff/developers](https://docs.djangoproject.com/en/3.1/howto/error-reporting/#email-reports)) enabled\n* A server-side error (HTTP 5xx) occurs during an attempt by a user to register an account\n\nUnder these conditions, recipients of the detailed error report will see all submitted data from the account-registration attempt, which may include the user's proposed credentials (such as a password).\n\n### Patches\n\nAs of version 3.1.2, django-registration properly applies Django's `sensitive_post_parameters()` decorator to the base user-registration view, which will cause all data from the HTTP request body to be filtered from detailed error reports in the event of a server-side crash during user account registration.\n\nNote that as applied, this filters *all* HTTP request data from error reports. To selectively allow some fields but not others, see Django's own documentation (in references) and the notes below for how to apply `sensitive_post_parameters()` manually to a particular codebase's `RegistrationView` subclass(es).\n\n### Workarounds\n\nUsers who cannot upgrade quickly can apply the `django.views.decorators.debug.sensitive_post_parameters()` decorator to their own registration views. The decorator should be applied on the `dispatch()` method of the appropriate `RegistrationView` class, using Django's `method_decorator()` helper. For example:\n\n```python\nfrom django.utils.decorators import method_decorator\nfrom django.views.decorators.debug import sensitive_post_parameters\n\nfrom django_registration.views import RegistrationView\n\nclass MyRegistrationView(RegistrationView):\n    \"\"\"\n    A RegistrationView subclass manually protected against sensitive information disclosure\n    in error reports.\n\n    \"\"\"\n    @method_decorator(sensitive_post_parameters())\n    def dispatch(self, *args, **kwargs):\n        return super().dispatch(*args, **kwargs)\n```\n\n### References\n\n* Django's documentation on [error reporting in production](https://docs.djangoproject.com/en/3.1/howto/error-reporting/)\n* [How Django's sensitive-data filters work](https://docs.djangoproject.com/en/3.1/howto/error-reporting/#filtering-error-reports)","status":"published","published":"2021-04-06T17:28:59Z","modified":"2026-07-08T06:27:33.519117704Z","cvss":[{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N","level":"low"},{"version":"4.0","score":2,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","level":"low"}],"cwes":["CWE-201","CWE-209"],"updated_at":"2026-11-02T15:46:38.213481Z"},{"id":"UBUNTU-CVE-2021-21416","description":"django-registration is a user registration package for Django. The django-registration package provides tools for implementing user-account registration flows in the Django web framework. In django-registration prior to 3.1.2, the base user-account registration view did not properly apply filters to sensitive data, with the result that sensitive data could be included in error reports rather than removed automatically by Django. Triggering this requires: A site is using django-registration \u003c 3.1.2, The site has detailed error reports (such as Django's emailed error reports to site staff/developers) enabled and a server-side error (HTTP 5xx) occurs during an attempt by a user to register an account. Under these conditions, recipients of the detailed error report will see all submitted data from the account-registration attempt, which may include the user's proposed credentials (such as a password).","status":"published","published":"2021-04-01T22:15:00Z","modified":"2026-10-17T12:56:19.331335141Z","cvss":[{"version":"3.1","score":3.7,"vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N","level":"low"},{"version":"3.1","score":2.6,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:N/A:N","level":"low"}],"updated_at":"2026-11-02T15:54:26.29421Z"},{"id":"MGASA-2022-0178","title":"Updated python-django-registration packages fix security vulnerability","description":"Sensitive data could be included in error reports (CVE-2021-21416)\n","status":"published","published":"2022-05-15T10:06:40Z","modified":"2026-04-16T04:43:15.490408752Z","updated_at":"2026-11-02T15:49:41.849028Z"},{"id":"openSUSE-SU-2021:0588-1","title":"Security update for python-django-registration","description":"This update for python-django-registration fixes the following issues:\n\nUpdate to 3.1.2 (boo#1184427, CVE-2021-21416)\n\n* Filter sensitive POST parameters in error reports\n* Fix RemovedInDjango40Warning from Signal arguments\n","status":"published","published":"2021-04-19T14:05:32Z","modified":"2026-02-04T03:09:38.073698Z","updated_at":"2026-11-02T16:58:31.879684Z"},{"id":"openSUSE-SU-2021:0597-1","title":"Security update for python-django-registration","description":"This update for python-django-registration fixes the following issues:\n\nUpdate to 3.1.2 (boo#1184427, CVE-2021-21416)\n\n* Filter sensitive POST parameters in error reports\n* Fix RemovedInDjango40Warning from Signal arguments\n\nThis update was imported from the openSUSE:Leap:15.2:Update update project.","status":"published","published":"2021-04-22T22:05:42Z","modified":"2026-02-04T02:39:56.165564Z","updated_at":"2026-11-02T16:58:31.879684Z"},{"id":"openSUSE-SU-2024:11226-1","title":"python36-django-registration-3.2-1.2 on GA media","description":"These are all security issues fixed in the python36-django-registration-3.2-1.2 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T03:48:12.252087Z","updated_at":"2026-11-02T16:58:34.894275Z"},{"id":"openSUSE-SU-2024:14138-1","title":"python310-django-registration-3.3-2.2 on GA media","description":"These are all security issues fixed in the python310-django-registration-3.3-2.2 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-07-12T00:00:00Z","modified":"2026-02-04T03:00:41.790897Z","updated_at":"2026-11-02T16:58:36.662953Z"},{"id":"openSUSE-SU-2026:12007-1","title":"python313-django-registration-5.2.1-1.3 on GA media","description":"These are all security issues fixed in the python313-django-registration-5.2.1-1.3 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-10-04T00:00:00Z","modified":"2026-10-05T10:15:46.321179287Z","updated_at":"2026-11-02T16:58:40.245664Z"},{"id":"PYSEC-2021-11","description":"django-registration is a user registration package for Django. The django-registration package provides tools for implementing user-account registration flows in the Django web framework. In django-registration prior to 3.1.2, the base user-account registration view did not properly apply filters to sensitive data, with the result that sensitive data could be included in error reports rather than removed automatically by Django. Triggering this requires: A site is using django-registration \u003c 3.1.2, The site has detailed error reports (such as Django's emailed error reports to site staff/developers) enabled and a server-side error (HTTP 5xx) occurs during an attempt by a user to register an account. Under these conditions, recipients of the detailed error report will see all submitted data from the account-registration attempt, which may include the user's proposed credentials (such as a password).","status":"published","published":"2021-04-01T22:15:00Z","modified":"2023-11-08T04:04:45.212413Z","updated_at":"2026-11-02T15:52:52.682031Z"}]}}