gVectors wpDiscuz up to 7.6.46 Shortcode do_shortcode code injection

Summaryinfo

A vulnerability has been found in gVectors wpDiscuz up to 7.6.46 and classified as critical. Affected by this vulnerability is the function do_shortcode of the component Shortcode Handler. The manipulation leads to code injection. This vulnerability is documented as CVE-2026-22191. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in gVectors wpDiscuz up to 7.6.46. It has been rated as critical. This issue affects the function do_shortcode of the component Shortcode Handler. The manipulation with an unknown input leads to a code injection vulnerability. Using CWE to declare the problem leads to CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

wpDiscuz before 7.6.47 contains a shortcode injection vulnerability that allows attackers to execute arbitrary shortcodes by including them in comment content sent via email notifications. Attackers can inject shortcodes like [contact-form-7] or [user_meta] in comments, which are executed server-side when the WpdiscuzHelperEmail class processes notifications through do_shortcode() before wp_mail().

The weakness was released by Scott Moore. The advisory is shared at wordpress.org. The identification of this vulnerability is CVE-2026-22191 since 01/06/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059 for this issue.

Upgrading to version 7.6.47 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• gVectors

Name

• wpDiscuz

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.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion