<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T22:07:14.002245+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-61663</id>
    <title>fkie_cve-2026-61663</title>
    <updated>2026-09-30T22:07:14.078410+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>django CMS is an easy-to-use and developer-friendly enterprise content management system powered by Django. Prior to 5.0.9, render_object_structure fails to authorize non-PageContent objects that use PlaceholderRelationField. An active staff user without cms.use_structure or model-level view or change permission can request the //admin/cms/placeholder/object/&lt;content_type_id&gt;/structure/&lt;object_id&gt;/ endpoint with guessed content_type_id and object_id values. The response discloses placeholder slot names, plugin trees, plugin identifiers, labels, and object existence for frontend-editable objects. The fix applies user_can_view_placeholder_source to the non-PageContent branch while keeping the structure board read-only for view-only users. This issue is fixed in versions 5.0.9.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-61663"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-8qj2-c6q4-f399</id>
    <title>GHSA-8qj2-c6q4-f399 — django CMS: Missing authorization in `render_object_structure` discloses non-PageContent placeholder structure to low-p…</title>
    <updated>2026-09-30T22:07:14.078672+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: django-cms</p>
<p>## Summary</p>
<p>The django-cms frontend-editing structure endpoint</p>
<p>```
GET /&lt;lang&gt;/admin/cms/placeholder/object/&lt;content_type_id&gt;/structure/&lt;object_id&gt;/
```</p>
<p>did not perform an object-level authorization check for **non-`PageContent`** objects. Any authenticated, active staff user could request the structure endpoint for a frontend-editable object (a model using `PlaceholderRelationField`) and read its placeholder/plugin structure, even without permission to change that object and without the `cms.use_structure` permission that the toolbar UI requires before offering structure mode.</p>
<p>`PageContent` objects were already protected (a page-view check added in GHSA/PR #8644); this advisory covers the remaining non-`PageContent` branch of the same view.</p>
<p>## Severity</p>
<p>The issue is staff-gated and read-only, disclosing CMS structure metadata (placeholder slot names, plugin tree, plugin identifiers/labels, object existence) rather than write access or arbitrary field data.</p>
<p>## Affected versions</p>
<p>- django-cms `&gt;= 4.0.0, &lt;= 5.0.x` and `5.1.0a1`
  (the vulnerable non-`PageContent` branch was introduced with the frontend-editing endpoints in 4.0)</p>
<p>## Patched versions</p>
<p>- django-cms TODO: 5.0.9</p>
<p>## Preconditions</p>
<p>- An authenticated, active staff account (`is_staff=True`).
- The deployment exposes a non-`PageContent` model with django-cms placeholders / frontend editing (e.g. via `PlaceholderRelationField`).
- The attacker can guess or enumerate the target `content_type_id` and object id.
- Th…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-8qj2-c6q4-f399"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2026-3823</id>
    <title>PYSEC-2026-3823 — django CMS: Missing authorization in `render_object_structure` discloses non-PageContent placeholder structure to low-p…</title>
    <updated>2026-09-30T22:07:14.078897+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: django-cms</p>
<p>## Summary</p>
<p>The django-cms frontend-editing structure endpoint</p>
<p>```
GET /&lt;lang&gt;/admin/cms/placeholder/object/&lt;content_type_id&gt;/structure/&lt;object_id&gt;/
```</p>
<p>did not perform an object-level authorization check for **non-`PageContent`** objects. Any authenticated, active staff user could request the structure endpoint for a frontend-editable object (a model using `PlaceholderRelationField`) and read its placeholder/plugin structure, even without permission to change that object and without the `cms.use_structure` permission that the toolbar UI requires before offering structure mode.</p>
<p>`PageContent` objects were already protected (a page-view check added in GHSA/PR #8644); this advisory covers the remaining non-`PageContent` branch of the same view.</p>
<p>## Severity</p>
<p>The issue is staff-gated and read-only, disclosing CMS structure metadata (placeholder slot names, plugin tree, plugin identifiers/labels, object existence) rather than write access or arbitrary field data.</p>
<p>## Affected versions</p>
<p>- django-cms `&gt;= 4.0.0, &lt;= 5.0.x` and `5.1.0a1`
  (the vulnerable non-`PageContent` branch was introduced with the frontend-editing endpoints in 4.0)</p>
<p>## Patched versions</p>
<p>- django-cms TODO: 5.0.9</p>
<p>## Preconditions</p>
<p>- An authenticated, active staff account (`is_staff=True`).
- The deployment exposes a non-`PageContent` model with django-cms placeholders / frontend editing (e.g. via `PlaceholderRelationField`).
- The attacker can guess or enumerate the target `content_type_id` and object id.
- Th…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2026-3823"/>
  </entry>
</feed>
