<?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:32:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-69139 — djangocms-moderation: Moderation comments disclosed to non-participant staff via the admin changelist</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-69139</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; django-cms djangocms-moderation&lt;/p&gt;
&lt;p&gt;djangocms-moderation provides an approval workflow mechanism for organizations that require content approval before publication. Prior to 2.4.0, CollectionCommentAdmin and RequestCommentAdmin in the Django admin use changelist_view and changeform_view to scope comment access through caller-controlled object identifiers and model-level view_collectioncomment or view_requestcomment permissions without invoking ModerationRequest.user_can_view_comments() or an equivalent collection participant check. An authenticated staff user with either view permission can enumerate collection or moderation-request identifiers and read full comment messages for workflows they do not participate in. The exposure affects confidentiality of internal editorial discussions; comment creation, modification, and deletion remain protected, and integrity and availability are unaffected. This issue is fixed in version 2.4.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; django-cms djangocms-moderation&lt;/p&gt;
&lt;p&gt;djangocms-moderation provides an approval workflow mechanism for organizations that require content approval before publication. Prior to 2.4.0, CollectionCommentAdmin and RequestCommentAdmin in the Django admin use changelist_view and changeform_view to scope comment access through caller-controlled object identifiers and model-level view_collectioncomment or view_requestcomment permissions without invoking ModerationRequest.user_can_view_comments() or an equivalent collection participant check. An authenticated staff user with either view permission can enumerate collection or moderation-request identifiers and read full comment messages for workflows they do not participate in. The exposure affects confidentiality of internal editorial discussions; comment creation, modification, and deletion remain protected, and integrity and availability are unaffected. This issue is fixed in version 2.4.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-69139</guid>
    </item>
  </channel>
</rss>
