<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 13:25:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-34406 — APTRS: Privilege Escalation via Mass Assignment of is_superuser in User Edit Endpoint</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-34406</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; APTRS&lt;/p&gt;
&lt;p&gt;APTRS (Automated Penetration Testing Reporting System) is a Python and Django-based automated reporting tool designed for penetration testers and security organizations. Prior to version 2.0.1, the edit_user endpoint (POST /api/auth/edituser/&amp;lt;pk&amp;gt;) allows Any user who can reach that endpoint and submit crafted permission to escalate their own account (or any other account) to superuser by including &amp;#34;is_superuser&amp;#34;: true in the request body. The root cause is that CustomUserSerializer explicitly includes is_superuser in its fields list but omits it from read_only_fields, making it a writable field. The edit_user view performs no additional validation to prevent non-superusers from modifying this field. Once is_superuser is set to true, gaining unrestricted access to all application functionality without requiring re-authentication. This issue has been patched in version 2.0.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; APTRS&lt;/p&gt;
&lt;p&gt;APTRS (Automated Penetration Testing Reporting System) is a Python and Django-based automated reporting tool designed for penetration testers and security organizations. Prior to version 2.0.1, the edit_user endpoint (POST /api/auth/edituser/&amp;lt;pk&amp;gt;) allows Any user who can reach that endpoint and submit crafted permission to escalate their own account (or any other account) to superuser by including &amp;#34;is_superuser&amp;#34;: true in the request body. The root cause is that CustomUserSerializer explicitly includes is_superuser in its fields list but omits it from read_only_fields, making it a writable field. The edit_user view performs no additional validation to prevent non-superusers from modifying this field. Once is_superuser is set to true, gaining unrestricted access to all application functionality without requiring re-authentication. This issue has been patched in version 2.0.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-34406</guid>
    </item>
  </channel>
</rss>
