How severe is CVE-2022-3688?

CVE-2022-3688 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2022-3688 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (38th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2022-3688?

CVE-2022-3688 affects 2code Wpqa Builder. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2022-3688?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2022-3688 published?

CVE-2022-3688 was published on 2022-11-21 and last updated on 2026-06-17.

CVE-2022-3688

CVE-2022-3688 is a high-severity vulnerability in 2code Wpqa Builder with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 8.8)
EPSS exploit prediction: 0% (38th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: 2code Wpqa Builder
Published: 2022-11-21
Last modified: 2026-06-17

Description

The WPQA Builder WordPress plugin before 5.9 does not have CSRF check when following and unfollowing users, which could allow attackers to make logged in users perform such actions via CSRF attacks

Frequently asked questions

What is CVE-2022-3688?: The WPQA Builder WordPress plugin before 5.9 does not have CSRF check when following and unfollowing users, which could allow attackers to make logged in users perform such actions via CSRF attacks
How severe is CVE-2022-3688?: CVE-2022-3688 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2022-3688 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (38th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-3688?: CVE-2022-3688 affects 2code Wpqa Builder. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-3688?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2022-3688 published?: CVE-2022-3688 was published on 2022-11-21 and last updated on 2026-06-17.

References

https://wpscan.com/vulnerability/03b2c6e6-b86e-4143-a84a-7a99060c4848

Affected products (1)

cpe:2.3:a:2code:wpqa_builder:*:*:*:*:*:wordpress:*:*

More vulnerabilities in 2code Wpqa Builder

CVE-2024-2376 — High (CVSS 8.8): The WPQA Builder WordPress plugin before 6.1.1 does not have CSRF checks in some places, which could allow attackers to…
CVE-2022-1597 — Medium (CVSS 6.1): The WPQA Builder WordPress plugin before 5.4, used as a companion for the Discy and Himer , does not sanitise and…
CVE-2024-2375 — Medium (CVSS 5.4): The WPQA Builder WordPress plugin before 6.1.1 does not sanitise and escape some of its Slider settings, which could…
CVE-2022-1051 — Medium (CVSS 5.4): The WPQA Builder Plugin WordPress plugin before 5.2, used as a companion plugin for the Discy and Himer , does not…
CVE-2022-1598 — Medium (CVSS 5.3): The WPQA Builder WordPress plugin before 5.5 which is a companion to the Discy and Himer , lacks authentication in a…
CVE-2022-2198 — Medium (CVSS 4.3): The WPQA Builder WordPress plugin before 5.7 which is a companion plugin to the Hilmer and Discy , does not check…

All CVEs affecting 2code Wpqa Builder →