Management-key disclosure via forged commenter cookie
Published Oct 16, 2026 · Updated Oct 16, 2026
Key disclosure in Subscribe to Comments before 2.3.3 allows remote attackers to alter subscriptions via a forged cookie. The plugin trusts an unsigned, unvalidated commenter-identification cookie and reveals the associated subscriber's management key. No authentication is required, and the disclosed key authorizes silent changes to that subscriber's subscriptions.
Summary
What happened
Key disclosure in Subscribe to Comments before 2.3.3 allows remote attackers to alter subscriptions via a forged cookie. The plugin trusts an unsigned, unvalidated commenter-identification cookie and reveals the associated subscriber's management key. No authentication is required, and the disclosed key authorizes silent changes to that subscriber's subscriptions.
The record
- CVE
- CVE-2026-91830
- Published
- Oct 16, 2026
- Updated
- Oct 16, 2026
- Vendor
- Mark Jaquith
- Product
- Subscribe to Comments
- Classifications
- CWE-200, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 16, 2026CVE publishedPublication date reported by the CVE source.
- Oct 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.3.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started