The plugin contains an issue with insufficiently protected credentials. The public click-tracking REST route `/tnp/l/` is registered with a `permission callback` set to ` return true`. When a valid keyed-MD5 signature is received, the `set user cookie()` function is called. Because the subscriber object loaded via `get user()` lacks the ` trusted` property, the `get user key()` function returns the raw token instead of an MD5-masked version, resulting in a `Set-Cookie: newsletter=<id>-<raw token>` response header. Unauthenticated attackers who obtain a signed click-tracking URL can use this to acquire a subscriber's permanent raw authentication cookie. This cookie allows the attacker to export full PII records via the `?na=px` endpoint, rewrite stored profiles via the `?na=ps` endpoint, or unsubscribe the user via the `?na=ocu` endpoint without requiring a nonce, password, or email challenge. These tracking URLs are embedded in external links, do not have timestamps, and do not expire until the site's relink key rotates.