---
id: "CVE-2026-91830"
kind: "vulnerability"
aliases: ["CVE-2026-91830"]
title: "WordPress Subscribe to Comments plugin: forged cookie exposes subscriber management keys"
severity: "medium"
cvss: 6.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "subscribe-to-comments", "wordpress", "wordpress-plugin"]
not_affected_if: ["plugin-2.3.3-or-later", "plugin-not-installed"]
published_at: "2026-10-16T07:17:13+00:00"
first_seen_at: "2026-10-23T21:57:12+00:00"
updated_at: "2026-10-25T03:57:58+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-91830", "first_seen_at": "2026-10-23T21:57:12+00:00"}]
---

# WordPress Subscribe to Comments plugin: forged cookie exposes subscriber management keys

The Subscribe to Comments WordPress plugin before 2.3.3 trusts an unsigned, unvalidated cookie to identify a commenter. An unauthenticated attacker can forge that cookie to read a subscriber's management key and change that subscriber's comment subscriptions.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed version of the Subscribe to Comments plugin in the WordPress admin under Plugins, or in `wp-content/plugins/` (version in the plugin header)
- unknown whether other check methods are needed

## Fix

- Update the Subscribe to Comments plugin to `2.3.3` or later
- unknown whether a workaround exists before updating

## Timeline

- 2026-10-23T21:57:12+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-91830

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_