Strategic Overview
- Status
- Patched in 1.7.0
- Affected Plugin
- wpForo Forum
- Affected Version
<= 1.6.5- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2019-19109
At a glance
CVE-2019-19109 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the wpForo Forum WordPress plugin, affecting versions <= 1.6.5. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.7.0; sites on affected versions should update now. Disclosed May 2020, reported by Sh0ckFR.
Vulnerability Overview
The wpForo plugin 1.6.5 for WordPress allows wp-admin/admin.php?page=wpforo-usergroups CSRF.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in wpForo Forum <= 1.6.5 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For wpForo Forum the fix is 1.7.0: builds <= 1.6.5 are affected, anything from 1.7.0 onward is not.
Remediation
Update to version 1.7.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to wpForo Forum: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: wpForo Forum 1.7.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 8.8CVE-2022-40192: wpForo Forum <= 2.0.9 Cross-Site Request Forgery
CVE-2022-40192 - 8.8CVE-2022-38144: wpForo Forum <= 2.0.5 Cross-Site Request Forgery
CVE-2022-38144 - 8.8CVE-2022-40632: wpForo Forum <= 2.0.5 Cross-Site Request Forgery
CVE-2022-40632 - 4.3CVE-2023-47870: wpForo Forum <= 2.2.8 Cross-Site Request Forgery
CVE-2023-47870
Other vulnerabilities in wpForo Forum
- 9.9CVE-2024-3200: wpForo Forum <= 2.3.3 SQL Injection
CVE-2024-3200 - 9.8CVE-2023-47868: wpForo Forum <= 2.2.3 Privilege Escalation
CVE-2023-47868 - 9.8CVE-2018-16613: wpForo < = 1.5.1 Privilege Escalation
CVE-2018-16613 - 9.8CVE-2018-11515: wpForo Forum <= 1.4.12 SQL Injection
CVE-2018-11515 - 8.8CVE-2026-3666: wpForo Forum <= 2.4.16 Arbitrary File Deletion
CVE-2026-3666 - 8.8CVE-2026-0910: wpForo Forum <= 2.4.13 PHP Object Injection
CVE-2026-0910 - 8.8CVE-2025-31420: wpForo Forum <= 2.4.3 Privilege Escalation
CVE-2025-31420 - 8.8CVE-2023-2249: wpForo Forum Local File Include, SSRF, and PHAR
CVE-2023-2249
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C