<?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>Sun, 04 Oct 2026 15:02:28 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-48094 — ShareOpenly has Cross-Site Scripting (XSS) via Missing esc_url() on Shared URL in Content Output</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-48094</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; dartiss shareopenly&lt;/p&gt;
&lt;p&gt;The ShareOpenly WordPress plugin prior to version 1.2.1 contains a Cross-Site Scripting vulnerability caused by the absence of WordPress&amp;#39;s `esc_url()` escaping function on the `$url` variable before it is rendered into HTML content. This variable is constructed from `home_url( add_query_arg( array(), $wp-&amp;gt;request ) )` and is concatenated directly into an HTML `href` attribute on every singular post or page where the plugin&amp;#39;s sharing link is displayed. WordPress&amp;#39;s security handbook mandates that every URL placed in HTML output must be passed through `esc_url()`, which both HTML-encodes special characters (converting `&amp;#34;`, `&amp;lt;`, `&amp;gt;` into their safe HTML entity equivalents) and strips dangerous URI schemes such as `javascript:` and `data:`. The omission of this function means that if the `$url` value ever contains HTML-special characters or a dangerous URI scheme — through a `home_url` WordPress filter applied by another plugin or theme, through certain web server or hosting configurations, or through future code changes — the unescaped content will be injected verbatim into the rendered HTML of every post or page on the site. Version 1.2.1 contains a patch for the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; dartiss shareopenly&lt;/p&gt;
&lt;p&gt;The ShareOpenly WordPress plugin prior to version 1.2.1 contains a Cross-Site Scripting vulnerability caused by the absence of WordPress&amp;#39;s `esc_url()` escaping function on the `$url` variable before it is rendered into HTML content. This variable is constructed from `home_url( add_query_arg( array(), $wp-&amp;gt;request ) )` and is concatenated directly into an HTML `href` attribute on every singular post or page where the plugin&amp;#39;s sharing link is displayed. WordPress&amp;#39;s security handbook mandates that every URL placed in HTML output must be passed through `esc_url()`, which both HTML-encodes special characters (converting `&amp;#34;`, `&amp;lt;`, `&amp;gt;` into their safe HTML entity equivalents) and strips dangerous URI schemes such as `javascript:` and `data:`. The omission of this function means that if the `$url` value ever contains HTML-special characters or a dangerous URI scheme — through a `home_url` WordPress filter applied by another plugin or theme, through certain web server or hosting configurations, or through future code changes — the unescaped content will be injected verbatim into the rendered HTML of every post or page on the site. Version 1.2.1 contains a patch for the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-48094</guid>
    </item>
  </channel>
</rss>
