VulnerabilityPublished 13 Mar 2026

CVE-2026-22203: wpDiscuz (WordPress plugin) · Information Exposure

Affects wpDiscuz (WordPress plugin)Source CVE Database V5

Compare

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

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

6.9Medium

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

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
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: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
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: 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 30 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-22203, organizations should immediately update wpDiscuz to version 7.6.47 or later where this vulnerability is addressed. Administrators should audit all exported plugin option files, support tickets, backups, and version control repositories for any plaintext OAuth secrets and rotate these credentials if they have been exposed. Implement strict access controls and encryption for any exported configuration files to prevent unauthorized access. Limit the number of administrators who can export plugin options and enforce least privilege principles. Additionally, monitor social login provider dashboards for suspicious activity that could indicate misuse of compromised secrets. Educate administrators about the risks of exporting sensitive configuration data and establish secure handling procedures. Finally, consider implementing multi-factor authentication on social login provider accounts to reduce the impact of credential exposure.

Description

CVE-2026-22203 is an information disclosure vulnerability in the wpDiscuz WordPress plugin before version 7.6.47. It allows administrators to inadvertently expose sensitive OAuth secrets such as Facebook App Secret, Google Client Secret, and Twitter App Secret by exporting plugin options as JSON. Attackers can obtain these plaintext API credentials from exported files found in support tickets, backups, or version control repositories. The vulnerability does not require user interaction but requires administrator privileges to trigger the export. The CVSS 4.0 base score is 6.9, indicating a medium severity level. Exploitation could lead to unauthorized access to social login integrations, potentially compromising user authentication and privacy.

Impact

The primary impact of this vulnerability is the exposure of sensitive OAuth credentials used for social login integrations within wpDiscuz. If attackers obtain these secrets, they can potentially impersonate the affected application to social login providers such as Facebook, Google, and Twitter. This could lead to unauthorized access to user accounts, data leakage, and compromise of user privacy. Organizations relying on wpDiscuz for community engagement and social login features may face reputational damage and regulatory consequences if user data is compromised. Additionally, the exposure of these secrets could facilitate further attacks such as account takeover or phishing campaigns leveraging the compromised social login tokens. Since the vulnerability requires administrator privileges to export the data, the risk is somewhat limited to scenarios where internal administrators mishandle exported files or where attackers have gained administrative access through other means. However, the widespread use of WordPress and wpDiscuz in various sectors including e-commerce, media, and education increases the potential attack surface globally.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats