VulnerabilityPublished 13 Mar 2026

CVE-2026-22182: gVectors wpDiscuz · Missing Authorization

Affects gVectors wpDiscuzSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 7.6.47 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score

8.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.6.47

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade gVectors wpDiscuz to 7.6.47.

Affected software

Product	Affected	Fixed in
gVectorswpDiscuz	Affected <7.6.47	Fixed in 7.6.47

AI-suggested

To mitigate CVE-2026-22182, organizations should immediately update the wpDiscuz plugin to version 7.6.47 or later, where the vulnerability is patched. If immediate patching is not feasible, administrators should implement temporary controls such as: 1) Restricting access to the wpdiscuz-ajax.php endpoint via web application firewall (WAF) rules or IP rate limiting to prevent abuse. 2) Enabling or enforcing CAPTCHA challenges on comment and notification-related AJAX requests to deter automated exploitation. 3) Monitoring outgoing email traffic for unusual spikes in notification emails and alerting on anomalies. 4) Reviewing and tightening WordPress user permissions and plugin configurations to minimize exposure. 5) Employing email rate limiting and spam filtering at the mail server level to reduce impact on recipients. Additionally, plugin developers and site administrators should audit other AJAX endpoints for similar missing authorization or nonce verification issues to prevent future vulnerabilities.

Description

CVE-2026-22182 is a high-severity unauthenticated denial of service vulnerability in the gVectors wpDiscuz plugin before version 7.6.47. The flaw allows anonymous attackers to exploit the checkNotificationType() function by repeatedly calling the wpdiscuz-ajax.php endpoint with arbitrary postId and comment_id parameters. This triggers mass notification emails to subscribers without any nonce verification, authentication, or rate limiting, resulting in email flooding. The vulnerability has a CVSS 4.0 score of 8.7, indicating a critical impact on availability with no user interaction or privileges required. No known exploits are currently reported in the wild.

Impact

The primary impact of CVE-2026-22182 is on the availability and user experience of websites using the vulnerable wpDiscuz plugin. Attackers can exploit this flaw to send mass notification emails to subscribers, potentially overwhelming email servers, causing service disruptions, and degrading the reputation of the affected domains due to spam-like behavior. This can lead to increased operational costs, blacklisting of email domains, and loss of user trust. Organizations relying on wpDiscuz for community engagement may face significant disruption in communication channels. Additionally, the flood of emails could be leveraged as a vector for social engineering or phishing if attackers combine this with malicious content. The vulnerability does not directly compromise confidentiality or integrity but can indirectly affect organizational operations and user confidence. Given the widespread use of WordPress and the popularity of wpDiscuz, the scope of affected systems is broad, impacting websites globally that have not updated to patched versions.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Mar 2026, 02:37 UTC

Technical details

References

Community reviews

Related threats