<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T12:33:43.624101+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2021-21416</id>
    <title>CVE-2021-21416 — Potential sensitive information disclosed in error reports</title>
    <updated>2026-10-07T12:33:43.659536+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> ubernostrum django-registration</p>
<p>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 &lt; 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).</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2021-21416"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-58c7-px5v-82hh</id>
    <title>GHSA-58c7-px5v-82hh — Potential sensitive information disclosed in error reports</title>
    <updated>2026-10-07T12:33:43.659609+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: django-registration</p>
<p>django-registration is a user-registration application for Django.</p>
<p>### Impact</p>
<p>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.</p>
<p>Triggering this requires the following conditions:</p>
<p>* A site is using django-registration &lt; 3.1.2
* 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
* A server-side error (HTTP 5xx) occurs during an attempt by a user to register an account</p>
<p>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).</p>
<p>### Patches</p>
<p>As 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.</p>
<p>Note that as applied, this filters *all* HTTP request data from error reports. To selectively allow some fields but not others, see Django's…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-58c7-px5v-82hh"/>
  </entry>
</feed>
