<?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://cve.radiocsirt.org</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>Tue, 27 Oct 2026 08:59:21 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-319603</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-319603</link>
      <description>EUVD-2026-319603</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-319603</guid>
    </item>
    <item>
      <title>fkie_cve-2026-6399</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-6399</link>
      <description>&lt;p&gt;The General Options plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 1.1.0. This is due to the use of sanitize_text_field() for output escaping in the Contact Number (ad_contact_number) field — a function that strips HTML tags but does not encode double-quote characters to their HTML entity equivalent (&amp;amp;quot;). When the stored value is echoed inside a double-quoted HTML attribute (value=&amp;#34;...&amp;#34;), an attacker-supplied double-quote character breaks out of the attribute context. Even with WordPress&amp;#39;s wp_magic_quotes mechanism (which prefixes quotes with a backslash), the resulting \&amp;#34; sequence is NOT treated as an escaped quote by HTML parsers — the backslash is rendered as a literal character and the bare double-quote still closes the attribute. This makes it possible for authenticated attackers with Administrator-level access and above to inject arbitrary web scripts in the admin settings page that will execute whenever any administrator visits the General Options settings page.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The General Options plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 1.1.0. This is due to the use of sanitize_text_field() for output escaping in the Contact Number (ad_contact_number) field — a function that strips HTML tags but does not encode double-quote characters to their HTML entity equivalent (&amp;amp;quot;). When the stored value is echoed inside a double-quoted HTML attribute (value=&amp;#34;...&amp;#34;), an attacker-supplied double-quote character breaks out of the attribute context. Even with WordPress&amp;#39;s wp_magic_quotes mechanism (which prefixes quotes with a backslash), the resulting \&amp;#34; sequence is NOT treated as an escaped quote by HTML parsers — the backslash is rendered as a literal character and the bare double-quote still closes the attribute. This makes it possible for authenticated attackers with Administrator-level access and above to inject arbitrary web scripts in the admin settings page that will execute whenever any administrator visits the General Options settings page.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-6399</guid>
    </item>
    <item>
      <title>GHSA-3hhp-2p2q-gg5w</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3hhp-2p2q-gg5w</link>
      <description>&lt;p&gt;The General Options plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 1.1.0. This is due to the use of sanitize_text_field() for output escaping in the Contact Number (ad_contact_number) field — a function that strips HTML tags but does not encode double-quote characters to their HTML entity equivalent (&amp;amp;quot;). When the stored value is echoed inside a double-quoted HTML attribute (value=&amp;#34;...&amp;#34;), an attacker-supplied double-quote character breaks out of the attribute context. Even with WordPress&amp;#39;s wp_magic_quotes mechanism (which prefixes quotes with a backslash), the resulting \&amp;#34; sequence is NOT treated as an escaped quote by HTML parsers — the backslash is rendered as a literal character and the bare double-quote still closes the attribute. This makes it possible for authenticated attackers with Administrator-level access and above to inject arbitrary web scripts in the admin settings page that will execute whenever any administrator visits the General Options settings page.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The General Options plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to and including 1.1.0. This is due to the use of sanitize_text_field() for output escaping in the Contact Number (ad_contact_number) field — a function that strips HTML tags but does not encode double-quote characters to their HTML entity equivalent (&amp;amp;quot;). When the stored value is echoed inside a double-quoted HTML attribute (value=&amp;#34;...&amp;#34;), an attacker-supplied double-quote character breaks out of the attribute context. Even with WordPress&amp;#39;s wp_magic_quotes mechanism (which prefixes quotes with a backslash), the resulting \&amp;#34; sequence is NOT treated as an escaped quote by HTML parsers — the backslash is rendered as a literal character and the bare double-quote still closes the attribute. This makes it possible for authenticated attackers with Administrator-level access and above to inject arbitrary web scripts in the admin settings page that will execute whenever any administrator visits the General Options settings page.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3hhp-2p2q-gg5w</guid>
    </item>
  </channel>
</rss>
