<?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>Thu, 01 Oct 2026 15:49:24 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-92537</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-92537</link>
      <description>&lt;p&gt;The Newsletter – Send awesome emails from WordPress plugin for WordPress is vulnerable to Insufficiently Protected Credentials in all versions up to, and including, 9.3.9 The plugin&amp;#39;s public click-tracking REST route `/tnp/l/` is registered with `permission_callback =&amp;gt; &amp;#39;__return_true&amp;#39;` and, upon receiving a valid keyed-MD5 signature, calls `set_user_cookie()`, which emits a `Set-Cookie: newsletter=&amp;lt;id&amp;gt;-&amp;lt;raw_token&amp;gt;` response header to the requester because the subscriber object loaded via `get_user()` lacks the `_trusted` property, causing `get_user_key()` to return the raw token column value instead of its MD5-masked variant. This makes it possible for unauthenticated attackers who obtain any signed click-tracking URL for a target subscriber to receive that subscriber&amp;#39;s permanent raw authentication cookie, which they can then use to export the subscriber&amp;#39;s full PII record via the JSON profile-export endpoint (`?na=px`), rewrite the subscriber&amp;#39;s stored profile (`?na=ps`), and silently unsubscribe the subscriber via the RFC-8058 one-click endpoint (`?na=ocu`), none of which require a nonce, password, or email challenge. Signed tracking URLs are embedded in every external link of every newsletter delivered to a subscriber, carry no timestamp, and never expire until the site&amp;#39;s relink key rotates, meaning that any party who observes such a URL — through a forwarded email, a shared inbox, a mail-gateway log, or Referer headers on the redirect target, which has no Referrer-Policy s…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Newsletter – Send awesome emails from WordPress plugin for WordPress is vulnerable to Insufficiently Protected Credentials in all versions up to, and including, 9.3.9 The plugin&amp;#39;s public click-tracking REST route `/tnp/l/` is registered with `permission_callback =&amp;gt; &amp;#39;__return_true&amp;#39;` and, upon receiving a valid keyed-MD5 signature, calls `set_user_cookie()`, which emits a `Set-Cookie: newsletter=&amp;lt;id&amp;gt;-&amp;lt;raw_token&amp;gt;` response header to the requester because the subscriber object loaded via `get_user()` lacks the `_trusted` property, causing `get_user_key()` to return the raw token column value instead of its MD5-masked variant. This makes it possible for unauthenticated attackers who obtain any signed click-tracking URL for a target subscriber to receive that subscriber&amp;#39;s permanent raw authentication cookie, which they can then use to export the subscriber&amp;#39;s full PII record via the JSON profile-export endpoint (`?na=px`), rewrite the subscriber&amp;#39;s stored profile (`?na=ps`), and silently unsubscribe the subscriber via the RFC-8058 one-click endpoint (`?na=ocu`), none of which require a nonce, password, or email challenge. Signed tracking URLs are embedded in every external link of every newsletter delivered to a subscriber, carry no timestamp, and never expire until the site&amp;#39;s relink key rotates, meaning that any party who observes such a URL — through a forwarded email, a shared inbox, a mail-gateway log, or Referer headers on the redirect target, which has no Referrer-Policy s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-92537</guid>
    </item>
    <item>
      <title>GHSA-r57r-xx5c-pcg3</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-r57r-xx5c-pcg3</link>
      <description>&lt;p&gt;The Newsletter – Send awesome emails from WordPress plugin for WordPress is vulnerable to Insufficiently Protected Credentials in all versions up to, and including, 9.3.9 The plugin&amp;#39;s public click-tracking REST route `/tnp/l/` is registered with `permission_callback =&amp;gt; &amp;#39;__return_true&amp;#39;` and, upon receiving a valid keyed-MD5 signature, calls `set_user_cookie()`, which emits a `Set-Cookie: newsletter=&amp;lt;id&amp;gt;-&amp;lt;raw_token&amp;gt;` response header to the requester because the subscriber object loaded via `get_user()` lacks the `_trusted` property, causing `get_user_key()` to return the raw token column value instead of its MD5-masked variant. This makes it possible for unauthenticated attackers who obtain any signed click-tracking URL for a target subscriber to receive that subscriber&amp;#39;s permanent raw authentication cookie, which they can then use to export the subscriber&amp;#39;s full PII record via the JSON profile-export endpoint (`?na=px`), rewrite the subscriber&amp;#39;s stored profile (`?na=ps`), and silently unsubscribe the subscriber via the RFC-8058 one-click endpoint (`?na=ocu`), none of which require a nonce, password, or email challenge. Signed tracking URLs are embedded in every external link of every newsletter delivered to a subscriber, carry no timestamp, and never expire until the site&amp;#39;s relink key rotates, meaning that any party who observes such a URL — through a forwarded email, a shared inbox, a mail-gateway log, or Referer headers on the redirect target, which has no Referrer-Policy s…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Newsletter – Send awesome emails from WordPress plugin for WordPress is vulnerable to Insufficiently Protected Credentials in all versions up to, and including, 9.3.9 The plugin&amp;#39;s public click-tracking REST route `/tnp/l/` is registered with `permission_callback =&amp;gt; &amp;#39;__return_true&amp;#39;` and, upon receiving a valid keyed-MD5 signature, calls `set_user_cookie()`, which emits a `Set-Cookie: newsletter=&amp;lt;id&amp;gt;-&amp;lt;raw_token&amp;gt;` response header to the requester because the subscriber object loaded via `get_user()` lacks the `_trusted` property, causing `get_user_key()` to return the raw token column value instead of its MD5-masked variant. This makes it possible for unauthenticated attackers who obtain any signed click-tracking URL for a target subscriber to receive that subscriber&amp;#39;s permanent raw authentication cookie, which they can then use to export the subscriber&amp;#39;s full PII record via the JSON profile-export endpoint (`?na=px`), rewrite the subscriber&amp;#39;s stored profile (`?na=ps`), and silently unsubscribe the subscriber via the RFC-8058 one-click endpoint (`?na=ocu`), none of which require a nonce, password, or email challenge. Signed tracking URLs are embedded in every external link of every newsletter delivered to a subscriber, carry no timestamp, and never expire until the site&amp;#39;s relink key rotates, meaning that any party who observes such a URL — through a forwarded email, a shared inbox, a mail-gateway log, or Referer headers on the redirect target, which has no Referrer-Policy s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-r57r-xx5c-pcg3</guid>
    </item>
  </channel>
</rss>
