<?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://vulnerability.circl.lu</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>Thu, 01 Oct 2026 23:33:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-63003 — django CMS: Broken access control in page *Duplicate* allows reading the content of any page (cross-site / restriction…</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-63003</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; django-cms&lt;/p&gt;
&lt;p&gt;django CMS is an easy-to-use and developer-friendly enterprise content management system powered by Django. Prior to 5.0.9, page duplication lacks an object-level authorization check on the source page. In cms/admin/forms.py, DuplicatePageForm.source accepts any Page, the AddPageForm constructor does not narrow a hidden source field, AddPageForm.clean does not validate the source against the user, and AddPageForm.save calls from_source. In cms/admin/pageadmin.py, duplicate and PageAdmin.has_add_permission check only whether a staff user may add a page. A crafted source value can therefore copy every placeholder and plugin from an unauthorized page with permissions=False, stripping source view restrictions and exposing content across sites or restricted subtrees when CMS_PERMISSION is enabled. This issue is fixed in versions 5.0.9.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; django-cms&lt;/p&gt;
&lt;p&gt;django CMS is an easy-to-use and developer-friendly enterprise content management system powered by Django. Prior to 5.0.9, page duplication lacks an object-level authorization check on the source page. In cms/admin/forms.py, DuplicatePageForm.source accepts any Page, the AddPageForm constructor does not narrow a hidden source field, AddPageForm.clean does not validate the source against the user, and AddPageForm.save calls from_source. In cms/admin/pageadmin.py, duplicate and PageAdmin.has_add_permission check only whether a staff user may add a page. A crafted source value can therefore copy every placeholder and plugin from an unauthorized page with permissions=False, stripping source view restrictions and exposing content across sites or restricted subtrees when CMS_PERMISSION is enabled. This issue is fixed in versions 5.0.9.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-63003</guid>
    </item>
    <item>
      <title>GHSA-6x92-6vx4-5fwr — django CMS: Broken access control in page *Duplicate* allows reading the content of any page (cross-site / restriction…</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-6x92-6vx4-5fwr</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: django-cms&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;The only authorization gate on the duplicate flow is `PageAdmin.has_add_permission`,
which checks `user_can_add_page(user, site)` / `user_can_add_subpage(...)` — i.e. *“may
this user create a page at all”*. Nothing checks the user’s relationship to the page being
copied:&lt;/p&gt;
&lt;p&gt;- `cms/admin/forms.py` — `DuplicatePageForm.source = ModelChoiceField(queryset=Page.objects.all(), widget=HiddenInput())`
  spans **every page in the database, on every site**.
- `cms/admin/forms.py` — `AddPageForm.__init__` returns early when the `source` widget is
  hidden, so the queryset is **never narrowed** to the user’s site/subtree.
- `cms/admin/forms.py` — `AddPageForm.clean()` validates only URL uniqueness; `source` is
  never validated against the user.
- `cms/admin/pageadmin.py` — `duplicate()` seeds `source` from the URL **only on GET**; on
  POST the value comes entirely from the request body.
- `cms/admin/forms.py` — `AddPageForm.save()` → `from_source()` performs
  `source.copy(..., permissions=False)` and copies **every placeholder and all plugins** of
  `source` into a new page on the attacker’s site. Because `permissions=False` drops the
  source’s view restrictions, the resulting copy is fully readable by the attacker.&lt;/p&gt;
&lt;p&gt;This crosses a real privilege boundary: a staff user restricted (via `CMS_PERMISSION`) to
their own site or subtree can exfiltrate the content of restricted pages and of pages
belonging to other tenants.&lt;/p&gt;
&lt;p&gt;**Read-back is trivial (verified):** the copy is created…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: django-cms&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;The only authorization gate on the duplicate flow is `PageAdmin.has_add_permission`,
which checks `user_can_add_page(user, site)` / `user_can_add_subpage(...)` — i.e. *“may
this user create a page at all”*. Nothing checks the user’s relationship to the page being
copied:&lt;/p&gt;
&lt;p&gt;- `cms/admin/forms.py` — `DuplicatePageForm.source = ModelChoiceField(queryset=Page.objects.all(), widget=HiddenInput())`
  spans **every page in the database, on every site**.
- `cms/admin/forms.py` — `AddPageForm.__init__` returns early when the `source` widget is
  hidden, so the queryset is **never narrowed** to the user’s site/subtree.
- `cms/admin/forms.py` — `AddPageForm.clean()` validates only URL uniqueness; `source` is
  never validated against the user.
- `cms/admin/pageadmin.py` — `duplicate()` seeds `source` from the URL **only on GET**; on
  POST the value comes entirely from the request body.
- `cms/admin/forms.py` — `AddPageForm.save()` → `from_source()` performs
  `source.copy(..., permissions=False)` and copies **every placeholder and all plugins** of
  `source` into a new page on the attacker’s site. Because `permissions=False` drops the
  source’s view restrictions, the resulting copy is fully readable by the attacker.&lt;/p&gt;
&lt;p&gt;This crosses a real privilege boundary: a staff user restricted (via `CMS_PERMISSION`) to
their own site or subtree can exfiltrate the content of restricted pages and of pages
belonging to other tenants.&lt;/p&gt;
&lt;p&gt;**Read-back is trivial (verified):** the copy is created…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-6x92-6vx4-5fwr</guid>
    </item>
  </channel>
</rss>
