<?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>Mon, 05 Oct 2026 17:44:14 +0000</lastBuildDate>
    <item>
      <title>BIT-phpmailer-2020-36326</title>
      <link>https://cve.radiocsirt.org/vuln/bit-phpmailer-2020-36326</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: phpmailer&lt;/p&gt;
&lt;p&gt;PHPMailer 6.1.8 through 6.4.0 allows object injection through Phar Deserialization via addAttachment with a UNC pathname. NOTE: this is similar to CVE-2018-19296, but arose because 6.1.8 fixed a functionality problem in which UNC pathnames were always considered unreadable by PHPMailer, even in safe contexts. As an unintended side effect, this fix eliminated the code that blocked addAttachment exploitation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: phpmailer&lt;/p&gt;
&lt;p&gt;PHPMailer 6.1.8 through 6.4.0 allows object injection through Phar Deserialization via addAttachment with a UNC pathname. NOTE: this is similar to CVE-2018-19296, but arose because 6.1.8 fixed a functionality problem in which UNC pathnames were always considered unreadable by PHPMailer, even in safe contexts. As an unintended side effect, this fix eliminated the code that blocked addAttachment exploitation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-phpmailer-2020-36326</guid>
    </item>
    <item>
      <title>certfr-2021-avi-378 — De multiples vulnérabilités ont été découvertes dans WordPress. Elles
permettent à un attaquant de provoquer une exécut…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2021-avi-378</link>
      <description>certfr-2021-avi-378</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2021-avi-378</guid>
    </item>
    <item>
      <title>cnvd-2021-73651</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2021-73651</link>
      <description>cnvd-2021-73651</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2021-73651</guid>
    </item>
    <item>
      <title>EUVD-2026-48133</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-48133</link>
      <description>EUVD-2026-48133</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-48133</guid>
    </item>
    <item>
      <title>fkie_cve-2020-36326</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-36326</link>
      <description>&lt;p&gt;PHPMailer 6.1.8 through 6.4.0 allows object injection through Phar Deserialization via addAttachment with a UNC pathname. NOTE: this is similar to CVE-2018-19296, but arose because 6.1.8 fixed a functionality problem in which UNC pathnames were always considered unreadable by PHPMailer, even in safe contexts. As an unintended side effect, this fix eliminated the code that blocked addAttachment exploitation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;PHPMailer 6.1.8 through 6.4.0 allows object injection through Phar Deserialization via addAttachment with a UNC pathname. NOTE: this is similar to CVE-2018-19296, but arose because 6.1.8 fixed a functionality problem in which UNC pathnames were always considered unreadable by PHPMailer, even in safe contexts. As an unintended side effect, this fix eliminated the code that blocked addAttachment exploitation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-36326</guid>
    </item>
    <item>
      <title>GHSA-m298-fh5c-jc66 — Object injection in PHPMailer/PHPMailer</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m298-fh5c-jc66</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: phpmailer/phpmailer&lt;/p&gt;
&lt;p&gt;### Impact
This is a reintroduction of an earlier issue (CVE-2018-19296) by an unrelated bug fix in PHPMailer 6.1.8.  An external file may be unexpectedly executable if it is used as a path to an attachment file via PHP&amp;#39;s support for `.phar` files. Exploitation requires that an attacker is able to provide an unfiltered path to a file to attach, or to trick calling code into generating one. See [this article](https://knasmueller.net/5-answers-about-php-phar-exploitation) for more info.&lt;/p&gt;
&lt;p&gt;### Patches
This issue was patched in the PHPMailer 6.4.1 release. This release also implements stricter filtering for attachment paths; paths that look like *any* kind of URL are rejected.&lt;/p&gt;
&lt;p&gt;### Workarounds
Validate paths to loaded files using the same pattern as used in [`isPermittedPath()`](https://github.com/PHPMailer/PHPMailer/blob/master/src/PHPMailer.php#L1815) before using them in *any* PHP file function, such as `file_exists`. This method can&amp;#39;t be used directly because it is protected, but you can implement the same thing in calling code. Note that this should be applied to *all* user-supplied paths passed into such functions; it&amp;#39;s not a problem specific to PHPMailer.&lt;/p&gt;
&lt;p&gt;### Credit
This issue was found by [Fariskhi Vidyan](https://github.com/farisv), reported and managed via Tidelift.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: phpmailer/phpmailer&lt;/p&gt;
&lt;p&gt;### Impact
This is a reintroduction of an earlier issue (CVE-2018-19296) by an unrelated bug fix in PHPMailer 6.1.8.  An external file may be unexpectedly executable if it is used as a path to an attachment file via PHP&amp;#39;s support for `.phar` files. Exploitation requires that an attacker is able to provide an unfiltered path to a file to attach, or to trick calling code into generating one. See [this article](https://knasmueller.net/5-answers-about-php-phar-exploitation) for more info.&lt;/p&gt;
&lt;p&gt;### Patches
This issue was patched in the PHPMailer 6.4.1 release. This release also implements stricter filtering for attachment paths; paths that look like *any* kind of URL are rejected.&lt;/p&gt;
&lt;p&gt;### Workarounds
Validate paths to loaded files using the same pattern as used in [`isPermittedPath()`](https://github.com/PHPMailer/PHPMailer/blob/master/src/PHPMailer.php#L1815) before using them in *any* PHP file function, such as `file_exists`. This method can&amp;#39;t be used directly because it is protected, but you can implement the same thing in calling code. Note that this should be applied to *all* user-supplied paths passed into such functions; it&amp;#39;s not a problem specific to PHPMailer.&lt;/p&gt;
&lt;p&gt;### Credit
This issue was found by [Fariskhi Vidyan](https://github.com/farisv), reported and managed via Tidelift.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m298-fh5c-jc66</guid>
    </item>
    <item>
      <title>gsd-2020-36326</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-36326</link>
      <description>gsd-2020-36326</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-36326</guid>
    </item>
    <item>
      <title>Withdrawn: UBUNTU-CVE-2020-36326</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-36326</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: libphp-phpmailer&lt;/p&gt;
&lt;p&gt;PHPMailer 6.1.8 through 6.4.0 allows object injection through Phar Deserialization via addAttachment with a UNC pathname. NOTE: this is similar to CVE-2018-19296, but arose because 6.1.8 fixed a functionality problem in which UNC pathnames were always considered unreadable by PHPMailer, even in safe contexts. As an unintended side effect, this fix eliminated the code that blocked addAttachment exploitation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: libphp-phpmailer&lt;/p&gt;
&lt;p&gt;PHPMailer 6.1.8 through 6.4.0 allows object injection through Phar Deserialization via addAttachment with a UNC pathname. NOTE: this is similar to CVE-2018-19296, but arose because 6.1.8 fixed a functionality problem in which UNC pathnames were always considered unreadable by PHPMailer, even in safe contexts. As an unintended side effect, this fix eliminated the code that blocked addAttachment exploitation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-36326</guid>
    </item>
  </channel>
</rss>
