Unauthenticated recipient manipulation via unsanitized cookie
Published Mar 13, 2026 · Updated Mar 13, 2026
Email header injection in gVectors Team wpDiscuz before 7.6.47 allows remote attackers to alter outgoing mail recipients via a cookie. The comment_author_email cookie is URL-decoded and passed unsanitized as a recipient to wp_mail(), so CRLF data becomes additional mail headers. No authentication is required, but a vulnerable mail path must process the crafted cookie; exploitation redirects or adds recipients without reading messages.
Summary
What happened
Email header injection in gVectors Team wpDiscuz before 7.6.47 allows remote attackers to alter outgoing mail recipients via a cookie. The comment_author_email cookie is URL-decoded and passed unsanitized as a recipient to wp_mail(), so CRLF data becomes additional mail headers. No authentication is required, but a vulnerable mail path must process the crafted cookie; exploitation redirects or adds recipients without reading messages.
The record
- CVE
- CVE-2026-22204
- Published
- Mar 13, 2026
- Updated
- Mar 13, 2026
- Vendor
- AdvancedCoding
- Product
- wpDiscuz
- Classifications
- CWE-20, T1565.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 13, 2026CVE publishedPublication date reported by the CVE source.
- Mar 13, 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 <7.6.47
What conditions does exploitation require?
What is affected?
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo