Subscribe to Comments: Sensitive information exposure
The Subscribe to Comments WordPress plugin before 2.3.3 does not sign or validate a cookie it trusts to identify a commenter, allowing unauthenticated attackers to disclose a subscriber's management key and silently alter that subscriber's subscriptions. The export supplies no additional endpoint, action, parameter or function details beyond those described above.
- Component
- Subscribe to Comments
- Plugin slug
subscribe-to-comments- Affected
- < 2.3.3
- Safe version
2.3.3- Published
- Oct 16, 2026
This CVE was published Oct 16, 2026 and is one of 7 known issues for this plugin.
Update, patch or deactivate.
Update Subscribe to Comments to 2.3.3 or a later supported release in the applicable branch. The completed authoritative record confirms this fixed version for the disclosed issue.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Subscribe to Comments WordPress plugin before 2.3.3 does not sign or validate a cookie it trusts to identify a commenter, allowing unauthenticated attackers to disclose a subscriber's management key and silently alter that subscriber's subscriptions.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N