VulnerabilityPublished 13 Mar 2026

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

Affects wpDiscuz (WordPress plugin)Source CVE Database V5

Compare

Not known to be exploited · CVSS 2.1 Low : upgrade to 7.6.47 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score

2.1Low

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

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: Low
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: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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

To mitigate CVE-2026-22210, organizations should immediately upgrade wpDiscuz to version 7.6.47 or later where the vulnerability is fixed. If upgrading is not immediately possible, administrators should restrict the ability to upload or modify attachments and filter hooks to trusted users only, minimizing the attack surface. Implementing a Web Application Firewall (WAF) with rules to detect and block suspicious script injections in comment attachments can provide temporary protection. Site administrators should audit existing attachments and filters for suspicious or malformed URLs and remove any untrusted content. Enforcing Content Security Policy (CSP) headers can help limit the impact of injected scripts by restricting script sources. Regularly monitoring logs for unusual comment activity or user reports of suspicious behavior is recommended. Finally, educating site users about the risks of interacting with untrusted comments and maintaining updated backups will aid in recovery if exploitation occurs.

Description

CVE-2026-22210 is a cross-site scripting (XSS) vulnerability in the gVectors wpDiscuz WordPress plugin versions before 7.6.47. The flaw arises from improper neutralization of input during web page generation, specifically through unescaped attachment URLs processed by the WpdiscuzHelperUpload class. Attackers can inject malicious JavaScript code into img and anchor tag attributes by crafting malicious attachment records or filter hooks. This code executes in the context of WordPress users viewing comments, potentially leading to session hijacking or other client-side attacks. The vulnerability requires low privileges and user interaction but does not compromise confidentiality, integrity, or availability directly. No known exploits are reported in the wild, and the CVSS 4.0 score is low (2.1).

Impact

The primary impact of CVE-2026-22210 is the potential execution of arbitrary JavaScript in the browsers of WordPress users viewing comments on sites using vulnerable wpDiscuz versions. This can lead to session hijacking, unauthorized actions performed on behalf of users, phishing attacks, or malware delivery. While the vulnerability does not directly compromise server-side confidentiality, integrity, or availability, it undermines user trust and can facilitate further attacks against site visitors. Organizations relying on wpDiscuz for comment functionality risk reputational damage and user data exposure if exploited. The low CVSS score reflects the limited scope and requirement for user interaction and partial privileges, but the widespread use of WordPress and popularity of wpDiscuz means many sites could be affected. Attackers with low privileges can leverage this flaw to escalate attacks against site users, especially if administrative users interact with malicious comments. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as proof-of-concept code could emerge.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats