gVectors wpDiscuz up to 7.6.46 wpdiscuz-ajax.php checkNotificationType comment_id authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in gVectors wpDiscuz up to 7.6.46. The impacted element is the function checkNotificationType of the file wpdiscuz-ajax.php. Such manipulation of the argument comment_id leads to authorization.
This vulnerability is documented as CVE-2026-22182. The attack can be executed remotely. There is not any exploit available.
You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in gVectors wpDiscuz up to 7.6.46. Affected by this issue is the function checkNotificationType of the file wpdiscuz-ajax.php. The manipulation of the argument comment_id with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Impacted is availability. CVE summarizes:
wpDiscuz before 7.6.47 contains an unauthenticated denial of service vulnerability that allows anonymous users to trigger mass notification emails by exploiting the checkNotificationType() function. Attackers can repeatedly call the wpdiscuz-ajax.php endpoint with arbitrary postId and comment_id parameters to flood subscribers with notifications, as the handler lacks nonce verification, authentication checks, and rate limiting.
The weakness was released by Scott Moore. The advisory is available at wordpress.org. This vulnerability is handled as CVE-2026-22182 since 01/06/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit.
By approaching the search of inurl:wpdiscuz-ajax.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 7.6.47 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
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: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
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: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Google Hack: 🔒
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-22182 (🔒)
GCVE (CVE): GCVE-0-2026-22182
GCVE (VulDB): GCVE-100-350786
Entry
Created: 03/13/2026 07:12Updated: 03/20/2026 03:50
Changes: 03/13/2026 07:12 (78), 03/20/2026 03:50 (1)
Complete: 🔍
Cache ID: 216:1F3:103
No comments yet. Languages: en.
Please log in to comment.