wpForo Forum vulnerabilities
Plugin slug wpforo · 59 known vulnerabilities · latest disclosed 2026-11-06 · WordPress.org page
Every listed vulnerability has a fix. Version 3.2.3 or later is not affected by any of them. If your site runs an older version, update it.
25 of 59 rated high or critical (CVSS 7 or more).
Known vulnerabilities in wpForo Forum
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| High 7.5 | <= 3.2.2 | 3.2.3 | CVE-2026-119164 | 2026-11-06 | Advisory |
| High 7.5 | <= 3.2.1 | 3.2.2 | CVE-2026-95870 | 2026-11-06 | Advisory |
| Medium 6.4 | <= 3.2.2 | 3.2.3 | CVE-2026-120532 | 2026-11-06 | Advisory |
| High 7.5 | <= 3.2.2 | 3.2.3 | CVE-2026-119155 | 2026-11-06 | Advisory |
| Medium 6.5 | <= 3.2.2 | 3.2.3 | CVE-2026-110004 | 2026-11-06 | Advisory |
| Medium 6.4 | <= 3.1.6 | 3.1.7 | CVE-2026-93747 | 2026-09-24 | Advisory |
| Medium 6.4 | <= 3.1.5 | 3.1.6 | CVE-2026-93772 | 2026-09-23 | Advisory |
| High 7.5 | <= 3.1.5 | 3.1.6 | CVE-2026-80513 | 2026-09-22 | Advisory |
| Medium 5.3 | 3.0.0 to 3.1.5 | 3.1.6 | CVE-2026-80514 | 2026-09-22 | Advisory |
| Medium 4.3 | <= 3.1.5 | 3.1.6 | CVE-2026-91092 | 2026-09-21 | Advisory |
| High 7.5 | <= 2.4.17 | 3.0.0 | CVE-2026-5097 | 2026-08-27 | Advisory |
| Medium 4.3 | <= 3.1.2 | 3.1.3 | CVE-2026-12698 | 2026-07-27 | Advisory |
| Medium 6.4 | <= 3.1.1 | 3.1.2 | CVE-2026-12696 | 2026-07-20 | Advisory |
| Medium 4.3 | <= 3.1.1 | 3.1.2 | CVE-2026-12697 | 2026-07-16 | Advisory |
| Medium 6.4 | <= 3.1.1 | 3.1.2 | CVE-2026-15021 | 2026-07-15 | Advisory |
| Medium 6.5 | <= 3.0.9 | 3.1.0 | CVE-2026-57636 | 2026-06-26 | Advisory |
| Medium 5.3 | <= 3.1.0 | 3.1.1 | CVE-2026-49767 | 2026-06-04 | Advisory |
| High 8.1 | <= 3.1.0 | 3.1.1 | CVE-2026-49769 | 2026-06-04 | Advisory |
| Medium 5.3 | <= 3.0.6 | 3.0.7 | CVE-2026-42682 | 2026-05-18 | Advisory |
| High 7.5 | <= 3.0.4 | 3.0.5 | CVE-2026-40798 | 2026-05-07 | Advisory |
| Medium 5.3 | < 3.0.2 | 3.0.2 | CVE-2026-40767 | 2026-04-21 | Advisory |
| High 8.1 | <= 3.0.5 | 3.0.6 | CVE-2026-6248 | 2026-04-20 | Advisory |
| Medium 6.5 | <= 2.4.16 | 3.0.0 | CVE-2026-4666 | 2026-04-16 | Advisory |
| High 7.1 | <= 3.0.2 | 3.0.3 | CVE-2026-5809 | 2026-04-10 | Advisory |
| High 8.8 | <= 2.4.16 | 2.4.17 | CVE-2026-3666 | 2026-04-03 | Advisory |
| High 7.5 | <= 2.4.14 | 2.4.15 | CVE-2026-1581 | 2026-02-18 | Advisory |
| High 8.8 | <= 2.4.13 | 2.4.14 | CVE-2026-0910 | 2026-02-10 | Advisory |
| High 7.5 | <= 2.4.12 | 2.4.13 | CVE-2025-13126 | 2025-12-13 | Advisory |
| Medium 5.3 | <= 2.4.10 | 2.4.11 | CVE-2025-66070 | 2025-11-18 | Advisory |
| Medium 6.5 | <= 2.4.9 | 2.4.10 | CVE-2025-11740 | 2025-10-31 | Advisory |
| High 7.5 | <= 2.4.8 | 2.4.9 | CVE-2025-4203 | 2025-10-24 | Advisory |
| Medium 4.3 | <= 2.4.6 | 2.4.7 | CVE-2025-58597 | 2025-09-03 | Advisory |
| Medium 5.4 | <= 2.4.5 | 2.4.6 | CVE-2025-4406 | 2025-07-09 | Advisory |
| High 8.8 | <= 2.4.3 | 2.4.4 | CVE-2025-31420 | 2025-04-02 | Advisory |
| Medium 6.5 | <= 2.4.1 | 2.4.2 | CVE-2025-0764 | 2025-02-27 | Advisory |
| Medium 5.3 | <= 2.3.4 | 2.3.5 | CVE-2024-43289 | 2024-08-16 | Advisory |
| Medium 4.3 | <= 2.3.4 | 2.3.5 | CVE-2024-43288 | 2024-08-16 | Advisory |
| Critical 9.9 | <= 2.3.3 | 2.3.4 | CVE-2024-3200 | 2024-05-31 | Advisory |
| Critical 9.8 | <= 2.2.3 | 2.2.4 | CVE-2023-47868 | 2023-11-20 | Advisory |
| Medium 4.3 | <= 2.2.8 | 2.2.9 | CVE-2023-47870 | 2023-11-20 | Advisory |
| Medium 6.4 | <= 2.2.3 | 2.2.4 | CVE-2023-47872 | 2023-11-20 | Advisory |
| Medium 4.3 | <= 2.2.5 | 2.2.6 | CVE-2023-47869 | 2023-11-20 | Advisory |
| Medium 6.1 | <= 2.1.8 | 2.1.9 | CVE-2023-2309 | 2023-07-03 | Advisory |
| High 8.8 | <= 2.1.7 | 2.1.8 | CVE-2023-2249 | 2023-06-01 | Advisory |
| Medium 5.4 | <= 2.0.9 | 2.1.0 | CVE-2022-38055 | 2022-12-07 | Advisory |
| Medium 6.3 | <= 2.0.5 | 2.0.6 | CVE-2022-40206 | 2022-11-26 | Advisory |
| High 8.8 | <= 2.0.9 | 2.1.0 | CVE-2022-40200 | 2022-11-09 | Advisory |
| High 8.8 | <= 2.0.9 | 2.1.0 | CVE-2022-40192 | 2022-11-09 | Advisory |
| Medium 5.4 | <= 2.0.5 | 2.0.6 | CVE-2022-40205 | 2022-09-26 | Advisory |
| High 8.8 | <= 2.0.5 | 2.0.6 | CVE-2022-38144 | 2022-09-08 | Advisory |
| High 8.8 | <= 2.0.5 | 2.0.6 | CVE-2022-40632 | 2022-09-08 | Advisory |
| Medium 6.1 | <= 1.9.6 | 1.9.7 | CVE-2021-24406 | 2021-06-14 | Advisory |
| Medium 6.1 | <= 1.6.5 | 1.7.0 | CVE-2019-19111 | 2020-05-04 | Advisory |
| High 8.8 | <= 1.6.5 | 1.7.0 | CVE-2019-19109 | 2020-05-04 | Advisory |
| Medium 6.1 | <= 1.6.5 | 1.7.0 | CVE-2019-19112 | 2020-05-04 | Advisory |
| Medium 4.8 | <= 1.6.5 | 1.7.0 | CVE-2019-19110 | 2020-05-04 | Advisory |
| Critical 9.8 | <= 1.5.1 | 1.5.2 | CVE-2018-16613 | 2018-09-06 | Advisory |
| Medium 6.1 | < 1.4.12 | 1.4.12 | CVE-2018-11709 | 2018-06-01 | Advisory |
| Critical 9.8 | <= 1.4.12 | 1.4.13 | CVE-2018-11515 | 2018-05-27 | Advisory |
Check if a site is affected
Enter a site address to see which version of wpForo Forum and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the wpForo Forum plugin safe to use?
All 59 known issues are fixed in current versions (3.2.3 or later). Keeping it updated is what matters.
How do I check which version of wpForo Forum my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.
Check any WordPress site in one click while you browse: Add PluginPeek to Chrome