Sender spoofing via unsanitized notification sender-name setting
Published Oct 19, 2026 · Updated Oct 19, 2026
Email header injection in Subscribe to Comments before 2.3.3 allows remote authenticated users to spoof senders via plugin settings. The notification sender-name setting accepts newline characters that become additional email headers, including a hidden Bcc. Author-level access or above is required, and the impact concerns outgoing notification messages rather than arbitrary code execution.
Summary
What happened
Email header injection in Subscribe to Comments before 2.3.3 allows remote authenticated users to spoof senders via plugin settings. The notification sender-name setting accepts newline characters that become additional email headers, including a hidden Bcc. Author-level access or above is required, and the impact concerns outgoing notification messages rather than arbitrary code execution.
The record
- CVE
- CVE-2026-91831
- Published
- Oct 19, 2026
- Updated
- Oct 19, 2026
- Vendor
- Mark Jaquith
- Product
- Subscribe to Comments
- Classifications
- CWE-93
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 19, 2026CVE publishedPublication date reported by the CVE source.
- Oct 19, 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=2.3 <2.3.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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