<?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, 05 Nov 2026 17:23:13 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-120552</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-120552</link>
      <description>&lt;p&gt;The SEO Engine – Smart SEO with AI, Schema &amp;amp; Redirection for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;title&amp;#39; parameter in all versions up to, and including, 0.9.9 due to insufficient input sanitization and output 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 accesses an injected page. WordPress core&amp;#39;s wp_filter_kses (applied via title_save_pre for Contributors and Authors) strips literal tag markup on save but leaves HTML-entity-encoded payloads intact in the database, meaning entity-encoded XSS payloads stored via the standard WordPress REST API (POST /wp-json/wp/v2/posts) are not neutralized before reaching the vulnerable sink.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The SEO Engine – Smart SEO with AI, Schema &amp;amp; Redirection for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;title&amp;#39; parameter in all versions up to, and including, 0.9.9 due to insufficient input sanitization and output 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 accesses an injected page. WordPress core&amp;#39;s wp_filter_kses (applied via title_save_pre for Contributors and Authors) strips literal tag markup on save but leaves HTML-entity-encoded payloads intact in the database, meaning entity-encoded XSS payloads stored via the standard WordPress REST API (POST /wp-json/wp/v2/posts) are not neutralized before reaching the vulnerable sink.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-120552</guid>
    </item>
    <item>
      <title>GHSA-x6h5-q644-mq4f</title>
      <link>https://db.gcve.eu/vuln/ghsa-x6h5-q644-mq4f</link>
      <description>&lt;p&gt;The SEO Engine – Smart SEO with AI, Schema &amp;amp; Redirection for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;title&amp;#39; parameter in all versions up to, and including, 0.9.9 due to insufficient input sanitization and output 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 accesses an injected page. WordPress core&amp;#39;s wp_filter_kses (applied via title_save_pre for Contributors and Authors) strips literal tag markup on save but leaves HTML-entity-encoded payloads intact in the database, meaning entity-encoded XSS payloads stored via the standard WordPress REST API (POST /wp-json/wp/v2/posts) are not neutralized before reaching the vulnerable sink.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The SEO Engine – Smart SEO with AI, Schema &amp;amp; Redirection for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;title&amp;#39; parameter in all versions up to, and including, 0.9.9 due to insufficient input sanitization and output 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 accesses an injected page. WordPress core&amp;#39;s wp_filter_kses (applied via title_save_pre for Contributors and Authors) strips literal tag markup on save but leaves HTML-entity-encoded payloads intact in the database, meaning entity-encoded XSS payloads stored via the standard WordPress REST API (POST /wp-json/wp/v2/posts) are not neutralized before reaching the vulnerable sink.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-x6h5-q644-mq4f</guid>
    </item>
  </channel>
</rss>
