VulnerabilityPublished 13 Mar 2026

CVE-2026-22183: wpDiscuz (WordPress plugin) · Cross-site Scripting

Affects wpDiscuz (WordPress plugin)Source CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 7.6.47 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 7% 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:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: Low
Subsequent system integrity: Low
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: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
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: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Subsequent System.
Subsequent system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent 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 wpDiscuz (WordPress plugin) to 7.6.47.

Affected software

Product	Affected	Fixed in
gVectorswpDiscuz	Affected <7.6.47	Fixed in 7.6.47

AI-suggested

Organizations should immediately upgrade wpDiscuz to version 7.6.47 or later once available, as this will contain the necessary patches to properly escape user input in AJAX responses. If you cannot patch yet, restrict the unfiltered_html capability to the minimum number of trusted users, ideally only site administrators, to reduce the risk of malicious comment injection. Implement additional input validation and output encoding on comment content at the application level if possible. Employ Web Application Firewalls (WAFs) with rules to detect and block suspicious script injections in comment submissions and AJAX responses. Regularly audit user roles and permissions to ensure no unnecessary privileges are granted. Monitor logs for unusual comment activity or AJAX requests that may indicate exploitation attempts. Educate content moderators and administrators about the risks of granting unfiltered_html capabilities. Consider disabling inline comment previews if they are not essential to reduce attack surface.

Description

CVE-2026-22183 is a stored cross-site scripting (XSS) vulnerability in the wpDiscuz WordPress plugin before version 7.6.47. It affects the inline comment preview functionality, allowing authenticated users with unfiltered_html capabilities to inject malicious JavaScript via comment content. The vulnerability arises because the getLastInlineComments() function in class. WpdiscuzHelperAjax.php does not properly escape HTML in AJAX responses. Exploitation requires user interaction and privileges to submit comments with unescaped content. The CVSS 4.0 base score is 5.

Impact

This vulnerability can lead to the execution of arbitrary JavaScript in the browsers of users who view the affected comments, compromising confidentiality and integrity of user sessions and data. Attackers could steal cookies, perform actions on behalf of other users, or deliver further malware payloads. While the vulnerability requires authenticated users with unfiltered_html capabilities, many WordPress sites grant this to trusted contributors or editors, increasing risk. The impact is primarily on the confidentiality and integrity of user data and site content, with limited direct availability impact. Exploitation could damage user trust and lead to reputational harm for affected organizations. Since wpDiscuz is a popular commenting plugin, many websites worldwide could be affected, especially those with active user communities and less restrictive user permissions. The absence of known exploits in the wild reduces immediate risk but does not eliminate the potential for future attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats