<?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://db.gcve.eu</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, 22 Oct 2026 14:42:23 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-112958</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-112958</link>
      <description>&lt;p&gt;ApostropheCMS is an open-source Node.js content management system. Prior to 4.34.0, a project-defined free-form widget style field can carry an editor-controlled quote into an inline style attribute because the wrapper serializer does not apply HTML-attribute encoding. The quote can terminate the style attribute and inject executable attributes when published content, or an affected draft viewed by a higher-privileged user, is rendered. This issue is fixed in version 4.34.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ApostropheCMS is an open-source Node.js content management system. Prior to 4.34.0, a project-defined free-form widget style field can carry an editor-controlled quote into an inline style attribute because the wrapper serializer does not apply HTML-attribute encoding. The quote can terminate the style attribute and inject executable attributes when published content, or an affected draft viewed by a higher-privileged user, is rendered. This issue is fixed in version 4.34.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-112958</guid>
    </item>
    <item>
      <title>GHSA-7jg5-frgc-c67w — ApostropheCMS: Stored XSS via Unescaped Widget Style Attribute Serialization</title>
      <link>https://db.gcve.eu/vuln/ghsa-7jg5-frgc-c67w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: apostrophe&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;ApostropheCMS widget styles support project-defined schema fields. If a project defines a free-form `string` style field with a CSS `property` and no selector, an editor-controlled value is rendered as an inline CSS declaration. The resulting declaration is then inserted into the widget wrapper&amp;#39;s `style=&amp;#34;...&amp;#34;` attribute without HTML-attribute escaping.&lt;/p&gt;
&lt;p&gt;An attacker who can edit the widget can include a double quote in the style value, terminate the `style` attribute, and inject new HTML event-handler attributes. The payload is stored with the widget and executes in the Apostrophe site origin whenever the affected published page is rendered.&lt;/p&gt;
&lt;p&gt;This is a sibling of CVE-2026-33889 / `GHSA-97v6-998m-fp4g`. The earlier issue escaped from a `&amp;lt;style&amp;gt;` element through a malicious color value. This variant reaches a different sink related to the automatically generated widget wrapper&amp;#39;s inline `style` and `class` attributes.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;### Root Cause 1: Free-form string style values retain HTML metacharacters&lt;/p&gt;
&lt;p&gt;The standard string field converter uses `launder.string()` and length validation. This performs type normalization, not output encoding for an HTML attribute context:&lt;/p&gt;
&lt;p&gt;[`packages/apostrophe/modules/@apostrophecms/schema/lib/addFieldTypes.js:296-333`](https://github.com/apostrophecms/apostrophe/blob/aa5170c7df9ff9ea5ac2e72a008f12e28dae6ca8/packages/apostrophe/modules/%40apostrophecms/schema/lib/addFieldTypes.js#L296-L333)&lt;/p&gt;
&lt;p&gt;```javascript
self.addFieldType({
  name: &amp;#39;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: apostrophe&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;ApostropheCMS widget styles support project-defined schema fields. If a project defines a free-form `string` style field with a CSS `property` and no selector, an editor-controlled value is rendered as an inline CSS declaration. The resulting declaration is then inserted into the widget wrapper&amp;#39;s `style=&amp;#34;...&amp;#34;` attribute without HTML-attribute escaping.&lt;/p&gt;
&lt;p&gt;An attacker who can edit the widget can include a double quote in the style value, terminate the `style` attribute, and inject new HTML event-handler attributes. The payload is stored with the widget and executes in the Apostrophe site origin whenever the affected published page is rendered.&lt;/p&gt;
&lt;p&gt;This is a sibling of CVE-2026-33889 / `GHSA-97v6-998m-fp4g`. The earlier issue escaped from a `&amp;lt;style&amp;gt;` element through a malicious color value. This variant reaches a different sink related to the automatically generated widget wrapper&amp;#39;s inline `style` and `class` attributes.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;### Root Cause 1: Free-form string style values retain HTML metacharacters&lt;/p&gt;
&lt;p&gt;The standard string field converter uses `launder.string()` and length validation. This performs type normalization, not output encoding for an HTML attribute context:&lt;/p&gt;
&lt;p&gt;[`packages/apostrophe/modules/@apostrophecms/schema/lib/addFieldTypes.js:296-333`](https://github.com/apostrophecms/apostrophe/blob/aa5170c7df9ff9ea5ac2e72a008f12e28dae6ca8/packages/apostrophe/modules/%40apostrophecms/schema/lib/addFieldTypes.js#L296-L333)&lt;/p&gt;
&lt;p&gt;```javascript
self.addFieldType({
  name: &amp;#39;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-7jg5-frgc-c67w</guid>
    </item>
  </channel>
</rss>
