CVE-2026-91831

Subscribe to Comments 2.3 - 2.3.2 - Author+ Email Header Injection via From Name Setting

LOW
3.8
CVSS Score
Published: October 19, 2026 at 06:46 AM UTC
Updated: October 19, 2026 at 09:02 PM UTC
1 product affected across 1 vendorSubscribe To Comments

Using Subscribe to Comments by Unknown?

Get instant alerts when new vulnerabilities affect Subscribe to Comments - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW3.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

The Subscribe to Comments WordPress plugin before 2.3.3 does not sanitise newline characters from a notification sender-name setting before using it in e-mail headers, allowing users with Author-level access and above to inject arbitrary e-mail headers, such as a hidden Bcc, and to spoof the sender.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (1)

ExploitVDB EntryTechnical Description
Source: cverecord
https://wpscan.com/vulnerability/6cd60f78-f5e2-4b4a-8d50-7d2bc4f981ee/

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

3.8LOWWPScan
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-93

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card