<?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, 01 Oct 2026 21:26:26 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-3853</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-3853</link>
      <description>&lt;p&gt;The Divi theme for WordPress is vulnerable to DOM-Based Stored Cross-Site Scripting via the `image_src` attribute of the `et_pb_video_slider_item` shortcode in all versions up to, and including, 4.27.6. This is due to the `image_src` field not being included in the `$url_options` whitelist (which only contains `url`, `button_link`, `button_url`), so it never receives `esc_url_raw()` at save time. On the server side, the value is rendered into a `data-image` HTML attribute using `esc_attr()`, which encodes double quotes as `&amp;amp;quot;`. However, the client-side JavaScript carousel code in `custom.unified.js` reads this attribute using jQuery&amp;#39;s `.data(&amp;#39;image&amp;#39;)`, which returns the browser-decoded value (with `&amp;amp;quot;` decoded back to `&amp;#34;`). The decoded value is then concatenated directly into an HTML string and injected into the DOM via `jQuery.after()` without re-escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user hovers over the carousel thumbnail.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Divi theme for WordPress is vulnerable to DOM-Based Stored Cross-Site Scripting via the `image_src` attribute of the `et_pb_video_slider_item` shortcode in all versions up to, and including, 4.27.6. This is due to the `image_src` field not being included in the `$url_options` whitelist (which only contains `url`, `button_link`, `button_url`), so it never receives `esc_url_raw()` at save time. On the server side, the value is rendered into a `data-image` HTML attribute using `esc_attr()`, which encodes double quotes as `&amp;amp;quot;`. However, the client-side JavaScript carousel code in `custom.unified.js` reads this attribute using jQuery&amp;#39;s `.data(&amp;#39;image&amp;#39;)`, which returns the browser-decoded value (with `&amp;amp;quot;` decoded back to `&amp;#34;`). The decoded value is then concatenated directly into an HTML string and injected into the DOM via `jQuery.after()` without re-escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user hovers over the carousel thumbnail.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-3853</guid>
    </item>
    <item>
      <title>GHSA-qpr5-j4j4-r5pg</title>
      <link>https://db.gcve.eu/vuln/ghsa-qpr5-j4j4-r5pg</link>
      <description>&lt;p&gt;The Divi theme for WordPress is vulnerable to DOM-Based Stored Cross-Site Scripting via the `image_src` attribute of the `et_pb_video_slider_item` shortcode in all versions up to, and including, 4.27.6. This is due to the `image_src` field not being included in the `$url_options` whitelist (which only contains `url`, `button_link`, `button_url`), so it never receives `esc_url_raw()` at save time. On the server side, the value is rendered into a `data-image` HTML attribute using `esc_attr()`, which encodes double quotes as `&amp;amp;quot;`. However, the client-side JavaScript carousel code in `custom.unified.js` reads this attribute using jQuery&amp;#39;s `.data(&amp;#39;image&amp;#39;)`, which returns the browser-decoded value (with `&amp;amp;quot;` decoded back to `&amp;#34;`). The decoded value is then concatenated directly into an HTML string and injected into the DOM via `jQuery.after()` without re-escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user hovers over the carousel thumbnail.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Divi theme for WordPress is vulnerable to DOM-Based Stored Cross-Site Scripting via the `image_src` attribute of the `et_pb_video_slider_item` shortcode in all versions up to, and including, 4.27.6. This is due to the `image_src` field not being included in the `$url_options` whitelist (which only contains `url`, `button_link`, `button_url`), so it never receives `esc_url_raw()` at save time. On the server side, the value is rendered into a `data-image` HTML attribute using `esc_attr()`, which encodes double quotes as `&amp;amp;quot;`. However, the client-side JavaScript carousel code in `custom.unified.js` reads this attribute using jQuery&amp;#39;s `.data(&amp;#39;image&amp;#39;)`, which returns the browser-decoded value (with `&amp;amp;quot;` decoded back to `&amp;#34;`). The decoded value is then concatenated directly into an HTML string and injected into the DOM via `jQuery.after()` without re-escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user hovers over the carousel thumbnail.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-qpr5-j4j4-r5pg</guid>
    </item>
  </channel>
</rss>
