← All security briefings

Attention

Subscribe2 10.50 stops forged one-click unsubscribe links

Identifiers: Subscribe2-10.50-security-release

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

Subscribe2 10.50, released 16 November 2026, fixes a weakness in the one-click unsubscribe link that the plugin inserts into notification emails through its unsubscribe tag. Those links could be forged, so anyone who knew a public subscriber's email address could remove that person from the list. Each link now carries a secret key and is only honoured when the key matches. The same release also fixes a bug where notification emails sent individually gave every recipient after the first the first recipient's unsubscribe link.

Classification reason: Based solely on the vendor changelog entry dated 16 November 2026 in the plugin readme at https://plugins.svn.wordpress.org/subscribe2/trunk/readme.txt, retrieved on 17 November 2026. No independent advisory was reviewed.

Impact

The weakness allowed removal of public subscribers without their consent. The changelog describes removal from the list and nothing beyond that: no disclosure of the subscriber list, account access or code execution is mentioned. A site could lose readers silently if someone targeted known addresses. The separate recipient mix-up meant a reader clicking what looked like their own link could unsubscribe someone else by accident.

Who is affected

WordPress sites running Subscribe2 with public subscribers whose notification emails use the one-click unsubscribe tag match the vendor's description. The changelog does not describe the effect on other subscription workflows, so their exposure is unknown. The vendor does not state which earlier versions are affected.

Products and versions

Products and versionsAffectedFixed
Subscribe2 Exact introduced/affected version range is not stated in the vendor changelog 10.50

Exploitation evidence

Exploitation not established. Exploitation status not established. The vendor changelog describes the fix and its side effect on older emails but does not mention active abuse.

Sources: Plugin vendor / WordPress SVN

Actions

  1. Update to 10.50 or later.
  2. Expect unsubscribe links in emails sent before the update to stop working; the vendor states subscribers can still unsubscribe through the subscription form, so mention that page in your next notification.
  3. Send a test notification to at least two addresses you control and confirm each email contains its own working unsubscribe link.
  4. Confirm the subscription page still lets a visitor unsubscribe.
  5. Watch subscriber counts for unexpected drops, and do not resend or republish old emails containing the previous links.

Unknowns

  • No CVE identifier or severity rating is given in the changelog.
  • The version that introduced the issue is not stated.
  • The changelog does not describe the effect on subscription workflows other than public subscribers receiving the one-click unsubscribe tag.
  • The vendor source contains no report of real-world abuse.

Sources

Change history

  1. — Published: Published 17 November 2026 from the vendor changelog for version 10.50 dated 16 November 2026.

Subscribe: RSS feed · JSON Feed · Feed format and fields