<?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>Wed, 30 Sep 2026 15:33:26 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-75526</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-75526</link>
      <description>&lt;p&gt;django CMS is an easy-to-use and developer-friendly enterprise content management system powered by Django. From 5.0.8 until 5.0.9, ContentRenderer.render_placeholder in cms/plugin_rendering.py can pass stored, attacker-controlled values to ContentRenderer.render_exception when plugin rendering fails in edit mode. Values from get_short_description(), the exception message, the placeholder, or placeholder.source are interpolated into a cms-rendering-exception heading and later returned through mark_safe. Because the heading is not escaped, stored HTML executes in an editor’s browser, and settings.DEBUG does not prevent the custom heading from rendering. The fix uses format_html to escape the message before safe placeholder output is returned. This issue is fixed in versions 5.0.9.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;django CMS is an easy-to-use and developer-friendly enterprise content management system powered by Django. From 5.0.8 until 5.0.9, ContentRenderer.render_placeholder in cms/plugin_rendering.py can pass stored, attacker-controlled values to ContentRenderer.render_exception when plugin rendering fails in edit mode. Values from get_short_description(), the exception message, the placeholder, or placeholder.source are interpolated into a cms-rendering-exception heading and later returned through mark_safe. Because the heading is not escaped, stored HTML executes in an editor’s browser, and settings.DEBUG does not prevent the custom heading from rendering. The fix uses format_html to escape the message before safe placeholder output is returned. This issue is fixed in versions 5.0.9.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-75526</guid>
    </item>
    <item>
      <title>GHSA-hvq6-2r72-p2x7 — django CMS: Stored XSS in edit-mode plugin exception rendering</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-hvq6-2r72-p2x7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: django-cms&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When plugin rendering fails in edit mode, django CMS renders a `cms-rendering-exception` block so editors can see that a placeholder could not be rendered. Older code built that block&amp;#39;s heading by interpolating the exception message, placeholder/source strings, and the failing plugin&amp;#39;s short description directly into an HTML string, then returned the placeholder output as safe markup.&lt;/p&gt;
&lt;p&gt;If an editor could store HTML in data used by a plugin&amp;#39;s `get_short_description()` (or in other values interpolated into the exception message), and that plugin later raised during edit-mode rendering, the payload was parsed as HTML in the staff user&amp;#39;s browser. This is a stored XSS condition in the CMS editing context.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;The vulnerable path is only reached when placeholder rendering catches a plugin rendering exception:&lt;/p&gt;
&lt;p&gt;```python
try:
    placeholder_content = &amp;#34;&amp;#34;.join(plugin_content)
except Exception as e:
    context[&amp;#34;exc_info&amp;#34;] = sys.exc_info()
    placeholder_content = self.render_exception(&amp;#34;rendering placeholder&amp;#34;, context, placeholder, editable)
```&lt;/p&gt;
&lt;p&gt;`render_exception()` constructs a `message` from values that can include stored content:&lt;/p&gt;
&lt;p&gt;- `value` - the exception message.
- `placeholder` - the placeholder string representation.
- `placeholder.source` - the source object string representation, such as page content.
- `instance.get_short_description()` - plugin-provided summary text, often derived from plugin model fields.&lt;/p&gt;
&lt;p&gt;In the vulnerable implementation, that messa…&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;## Summary&lt;/p&gt;
&lt;p&gt;When plugin rendering fails in edit mode, django CMS renders a `cms-rendering-exception` block so editors can see that a placeholder could not be rendered. Older code built that block&amp;#39;s heading by interpolating the exception message, placeholder/source strings, and the failing plugin&amp;#39;s short description directly into an HTML string, then returned the placeholder output as safe markup.&lt;/p&gt;
&lt;p&gt;If an editor could store HTML in data used by a plugin&amp;#39;s `get_short_description()` (or in other values interpolated into the exception message), and that plugin later raised during edit-mode rendering, the payload was parsed as HTML in the staff user&amp;#39;s browser. This is a stored XSS condition in the CMS editing context.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;The vulnerable path is only reached when placeholder rendering catches a plugin rendering exception:&lt;/p&gt;
&lt;p&gt;```python
try:
    placeholder_content = &amp;#34;&amp;#34;.join(plugin_content)
except Exception as e:
    context[&amp;#34;exc_info&amp;#34;] = sys.exc_info()
    placeholder_content = self.render_exception(&amp;#34;rendering placeholder&amp;#34;, context, placeholder, editable)
```&lt;/p&gt;
&lt;p&gt;`render_exception()` constructs a `message` from values that can include stored content:&lt;/p&gt;
&lt;p&gt;- `value` - the exception message.
- `placeholder` - the placeholder string representation.
- `placeholder.source` - the source object string representation, such as page content.
- `instance.get_short_description()` - plugin-provided summary text, often derived from plugin model fields.&lt;/p&gt;
&lt;p&gt;In the vulnerable implementation, that messa…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-hvq6-2r72-p2x7</guid>
    </item>
    <item>
      <title>PYSEC-2026-3825 — django CMS: Stored XSS in edit-mode plugin exception rendering</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2026-3825</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: django-cms&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When plugin rendering fails in edit mode, django CMS renders a `cms-rendering-exception` block so editors can see that a placeholder could not be rendered. Older code built that block&amp;#39;s heading by interpolating the exception message, placeholder/source strings, and the failing plugin&amp;#39;s short description directly into an HTML string, then returned the placeholder output as safe markup.&lt;/p&gt;
&lt;p&gt;If an editor could store HTML in data used by a plugin&amp;#39;s `get_short_description()` (or in other values interpolated into the exception message), and that plugin later raised during edit-mode rendering, the payload was parsed as HTML in the staff user&amp;#39;s browser. This is a stored XSS condition in the CMS editing context.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;The vulnerable path is only reached when placeholder rendering catches a plugin rendering exception:&lt;/p&gt;
&lt;p&gt;```python
try:
    placeholder_content = &amp;#34;&amp;#34;.join(plugin_content)
except Exception as e:
    context[&amp;#34;exc_info&amp;#34;] = sys.exc_info()
    placeholder_content = self.render_exception(&amp;#34;rendering placeholder&amp;#34;, context, placeholder, editable)
```&lt;/p&gt;
&lt;p&gt;`render_exception()` constructs a `message` from values that can include stored content:&lt;/p&gt;
&lt;p&gt;- `value` - the exception message.
- `placeholder` - the placeholder string representation.
- `placeholder.source` - the source object string representation, such as page content.
- `instance.get_short_description()` - plugin-provided summary text, often derived from plugin model fields.&lt;/p&gt;
&lt;p&gt;In the vulnerable implementation, that messa…&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;## Summary&lt;/p&gt;
&lt;p&gt;When plugin rendering fails in edit mode, django CMS renders a `cms-rendering-exception` block so editors can see that a placeholder could not be rendered. Older code built that block&amp;#39;s heading by interpolating the exception message, placeholder/source strings, and the failing plugin&amp;#39;s short description directly into an HTML string, then returned the placeholder output as safe markup.&lt;/p&gt;
&lt;p&gt;If an editor could store HTML in data used by a plugin&amp;#39;s `get_short_description()` (or in other values interpolated into the exception message), and that plugin later raised during edit-mode rendering, the payload was parsed as HTML in the staff user&amp;#39;s browser. This is a stored XSS condition in the CMS editing context.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;The vulnerable path is only reached when placeholder rendering catches a plugin rendering exception:&lt;/p&gt;
&lt;p&gt;```python
try:
    placeholder_content = &amp;#34;&amp;#34;.join(plugin_content)
except Exception as e:
    context[&amp;#34;exc_info&amp;#34;] = sys.exc_info()
    placeholder_content = self.render_exception(&amp;#34;rendering placeholder&amp;#34;, context, placeholder, editable)
```&lt;/p&gt;
&lt;p&gt;`render_exception()` constructs a `message` from values that can include stored content:&lt;/p&gt;
&lt;p&gt;- `value` - the exception message.
- `placeholder` - the placeholder string representation.
- `placeholder.source` - the source object string representation, such as page content.
- `instance.get_short_description()` - plugin-provided summary text, often derived from plugin model fields.&lt;/p&gt;
&lt;p&gt;In the vulnerable implementation, that messa…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2026-3825</guid>
    </item>
  </channel>
</rss>
