<?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>Sun, 22 Nov 2026 20:12:03 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-408992</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-408992</link>
      <description>EUVD-2026-408992</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-408992</guid>
    </item>
    <item>
      <title>fkie_cve-2026-69138</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-69138</link>
      <description>&lt;p&gt;djangocms-versioning is a general-purpose versioning package for django CMS 4 and later. Prior to 2.6.1, the check_discard and check_edit_redirect Conditions on djangocms_versioning.models.Version omit user_can_change, while VersionAdmin.discard_view and VersionAdmin.edit_redirect_view obtain a version by its primary key and rely on those conditions for object-level authorization. With CMS_PERMISSION set to True, the affected views are gated only by is_staff, allowing any staff user to select content without object-level change permission. With the default CMS_PERMISSION value of False, a staff user must also hold the global Django change_ permission, but that model-level permission does not enforce the intended per-object authorization, so the user can delete a draft version and its content object through discard or create an editable draft from a published version through edit_redirect even when the user cannot change that specific content object. This issue is fixed in version 2.6.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;djangocms-versioning is a general-purpose versioning package for django CMS 4 and later. Prior to 2.6.1, the check_discard and check_edit_redirect Conditions on djangocms_versioning.models.Version omit user_can_change, while VersionAdmin.discard_view and VersionAdmin.edit_redirect_view obtain a version by its primary key and rely on those conditions for object-level authorization. With CMS_PERMISSION set to True, the affected views are gated only by is_staff, allowing any staff user to select content without object-level change permission. With the default CMS_PERMISSION value of False, a staff user must also hold the global Django change_ permission, but that model-level permission does not enforce the intended per-object authorization, so the user can delete a draft version and its content object through discard or create an editable draft from a published version through edit_redirect even when the user cannot change that specific content object. This issue is fixed in version 2.6.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-69138</guid>
    </item>
    <item>
      <title>GHSA-5g9x-qwh5-33x4 — djangocms-versioning: Authorization Bypass Through User-Controlled Key and Missing Authorization</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5g9x-qwh5-33x4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: djangocms-versioning&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The `discard` and `edit_redirect` version transitions did not enforce a per-object change-permission check, while the sibling transitions (`archive`, `publish`, `unpublish`, `revert`) all did. As a result a low-privileged staff user could **discard (delete) any draft version — and thereby the underlying content object — of content they have no change permission on**, and could create an editable draft off any published version, by supplying a version primary key they should not have access to (an insecure direct object reference).&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;Version state transitions are guarded by `Conditions` objects declared on `djangocms_versioning.models.Version`. Every transition that mutates content carries the `user_can_change` condition, which delegates to the *content* object&amp;#39;s own permission check (`Version.has_change_permission` → `content.has_change_permission` / `has_placeholder_change_permission`, with a final fallback to the Django `change_&amp;lt;model&amp;gt;` permission).&lt;/p&gt;
&lt;p&gt;Two conditions were missing that check:&lt;/p&gt;
&lt;p&gt;```python
# Before (vulnerable)
check_discard = Conditions([
    in_state([constants.DRAFT], not_draft_error),
    is_not_locked(lock_error_message),
])
check_edit_redirect = Conditions([
    in_state([constants.DRAFT, constants.PUBLISHED], _(&amp;#34;Version is not in draft or published state&amp;#34;)),
    draft_is_not_locked(lock_draft_error_message),
])
```&lt;/p&gt;
&lt;p&gt;The corresponding admin views authorize **only** through these conditions:&lt;/p&gt;
&lt;p&gt;* `VersionAdmin.discard_view` / `VersionAd…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: djangocms-versioning&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The `discard` and `edit_redirect` version transitions did not enforce a per-object change-permission check, while the sibling transitions (`archive`, `publish`, `unpublish`, `revert`) all did. As a result a low-privileged staff user could **discard (delete) any draft version — and thereby the underlying content object — of content they have no change permission on**, and could create an editable draft off any published version, by supplying a version primary key they should not have access to (an insecure direct object reference).&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;Version state transitions are guarded by `Conditions` objects declared on `djangocms_versioning.models.Version`. Every transition that mutates content carries the `user_can_change` condition, which delegates to the *content* object&amp;#39;s own permission check (`Version.has_change_permission` → `content.has_change_permission` / `has_placeholder_change_permission`, with a final fallback to the Django `change_&amp;lt;model&amp;gt;` permission).&lt;/p&gt;
&lt;p&gt;Two conditions were missing that check:&lt;/p&gt;
&lt;p&gt;```python
# Before (vulnerable)
check_discard = Conditions([
    in_state([constants.DRAFT], not_draft_error),
    is_not_locked(lock_error_message),
])
check_edit_redirect = Conditions([
    in_state([constants.DRAFT, constants.PUBLISHED], _(&amp;#34;Version is not in draft or published state&amp;#34;)),
    draft_is_not_locked(lock_draft_error_message),
])
```&lt;/p&gt;
&lt;p&gt;The corresponding admin views authorize **only** through these conditions:&lt;/p&gt;
&lt;p&gt;* `VersionAdmin.discard_view` / `VersionAd…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5g9x-qwh5-33x4</guid>
    </item>
  </channel>
</rss>
