<?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>Fri, 16 Oct 2026 08:52:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43977 — wger IDOR: Authenticated Users Can Read Others' Private Workout Session Data via Template Routine API</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-43977</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; wger-project wger&lt;/p&gt;
&lt;p&gt;wger is a free, open-source workout and fitness manager. In versions prior to 2.6, any authenticated user can read another user&amp;#39;s private workout session notes, exercise history, and training statistics by calling the /logs/ and /stats/ actions on a routine they do not own. The vulnerability exists in RoutineViewSet (wger/manager/api/views.py). The view defines two custom actions /logs/ and /stats/ that are intended to return data for the requesting user&amp;#39;s own training history within a routine. However, the underlying permission check (RoutinePermission.has_object_permission) grants read access to any authenticated user when the routine has is_template=True, regardless of ownership. When the /logs/ or /stats/ actions are invoked against a routine the attacker does not own, they return the owner&amp;#39;s private workout history, not the attacker&amp;#39;s. This issue has been fixed in version 2.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; wger-project wger&lt;/p&gt;
&lt;p&gt;wger is a free, open-source workout and fitness manager. In versions prior to 2.6, any authenticated user can read another user&amp;#39;s private workout session notes, exercise history, and training statistics by calling the /logs/ and /stats/ actions on a routine they do not own. The vulnerability exists in RoutineViewSet (wger/manager/api/views.py). The view defines two custom actions /logs/ and /stats/ that are intended to return data for the requesting user&amp;#39;s own training history within a routine. However, the underlying permission check (RoutinePermission.has_object_permission) grants read access to any authenticated user when the routine has is_template=True, regardless of ownership. When the /logs/ or /stats/ actions are invoked against a routine the attacker does not own, they return the owner&amp;#39;s private workout history, not the attacker&amp;#39;s. This issue has been fixed in version 2.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-43977</guid>
    </item>
  </channel>
</rss>
