gVectors wpDiscuz up to 7.6.46 Cookie urldecode comment_author_email injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in gVectors wpDiscuz up to 7.6.46. It has been classified as problematic. This affects the function urldecode of the component Cookie Handler. This manipulation of the argument comment_author_email causes injection.
This vulnerability appears as CVE-2026-22204. The attack may be initiated remotely. There is no available exploit.
Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic was found in gVectors wpDiscuz up to 7.6.46. Affected by this vulnerability is the function urldecode of the component Cookie Handler. The manipulation of the argument comment_author_email with an unknown input leads to a injection vulnerability. The CWE definition for the vulnerability is CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
wpDiscuz before 7.6.47 contains an email header injection vulnerability that allows attackers to manipulate mail recipients by injecting malicious data into the comment_author_email cookie. Attackers can craft a malicious cookie value that, when processed through urldecode() and passed to wp_mail() functions, enables header injection to alter email recipients or inject additional headers.
The weakness was presented by Scott Moore. It is possible to read the advisory at wordpress.org. This vulnerability is known as CVE-2026-22204 since 01/06/2026. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1055 according to MITRE ATT&CK.
Upgrading to version 7.6.47 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
- 7.6.0
- 7.6.1
- 7.6.2
- 7.6.3
- 7.6.4
- 7.6.5
- 7.6.6
- 7.6.7
- 7.6.8
- 7.6.9
- 7.6.10
- 7.6.11
- 7.6.12
- 7.6.13
- 7.6.14
- 7.6.15
- 7.6.16
- 7.6.17
- 7.6.18
- 7.6.19
- 7.6.20
- 7.6.21
- 7.6.22
- 7.6.23
- 7.6.24
- 7.6.25
- 7.6.26
- 7.6.27
- 7.6.28
- 7.6.29
- 7.6.30
- 7.6.31
- 7.6.32
- 7.6.33
- 7.6.34
- 7.6.35
- 7.6.36
- 7.6.37
- 7.6.38
- 7.6.39
- 7.6.40
- 7.6.41
- 7.6.42
- 7.6.43
- 7.6.44
- 7.6.45
- 7.6.46
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔒
CNA Base Score: 3.7
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: InjectionCWE: CWE-74 / CWE-707 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: wpDiscuz 7.6.47
Timeline
01/06/2026 CVE reserved03/13/2026 Advisory disclosed
03/13/2026 VulDB entry created
03/20/2026 VulDB entry last update
Sources
Advisory: wordpress.orgResearcher: Scott Moore
Status: Confirmed
CVE: CVE-2026-22204 (🔒)
GCVE (CVE): GCVE-0-2026-22204
GCVE (VulDB): GCVE-100-350803
Entry
Created: 03/13/2026 07:23Updated: 03/20/2026 04:22
Changes: 03/13/2026 07:23 (79), 03/20/2026 04:22 (12)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.