gVectors wpDiscuz up to 7.6.46 getFollowsPage cross-site request forgery

Summaryinfo

A vulnerability was found in gVectors wpDiscuz up to 7.6.46. It has been classified as problematic. Impacted is the function getFollowsPage. Performing a manipulation results in cross-site request forgery. This vulnerability is reported as CVE-2026-22215. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in gVectors wpDiscuz up to 7.6.46. It has been classified as problematic. This affects the function getFollowsPage. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. The summary by CVE is:

wpDiscuz before 7.6.47 contains a cross-site request forgery vulnerability in the getFollowsPage() function that allows attackers to trigger unauthorized actions without nonce validation. Attackers can craft malicious requests to enumerate follow relationships and manipulate user follow data by exploiting the missing CSRF protection in the follows page handler.

The weakness was disclosed by Scott Moore. The advisory is shared at wordpress.org. This vulnerability is uniquely identified as CVE-2026-22215 since 01/06/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.

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