NEX-Forms
by WordPress
CVEs (8)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2022-3142 | Hig | 0.61 | 8.8 | 0.10 | Sep 19, 2022 | The NEX-Forms WordPress plugin before 7.9.7 does not properly sanitise and escape user input before using it in SQL statements, leading to SQL injections. The attack can be executed by anyone who is permitted to view the forms statistics chart, by default administrators, however… | ||
| CVE-2023-2114 | Hig | 0.50 | 7.2 | 0.45 | May 8, 2023 | The NEX-Forms WordPress plugin before 8.4 does not properly escape the `table` parameter, which is populated with user input, before concatenating it to an SQL query. | ||
| CVE-2021-34676 | Hig | 0.49 | 7.5 | 0.02 | Jul 19, 2021 | Basix NEX-Forms through 7.8.7 allows authentication bypass for Excel report generation. | ||
| CVE-2021-34675 | Hig | 0.49 | 7.5 | 0.02 | Jul 19, 2021 | Basix NEX-Forms through 7.8.7 allows authentication bypass for stored PDF reports. | ||
| CVE-2023-52120 | Med | 0.35 | 5.4 | 0.00 | Jan 5, 2024 | Cross-Site Request Forgery (CSRF) vulnerability in Basix NEX-Forms – Ultimate Form Builder – Contact forms and much more.This issue affects NEX-Forms – Ultimate Form Builder – Contact forms and much more: from n/a through 8.5.2. | ||
| CVE-2023-0439 | Med | 0.35 | 5.4 | 0.00 | Jul 17, 2023 | The NEX-Forms WordPress plugin before 8.4.4 does not escape its form name, which could lead to Stored Cross-Site Scripting issues. By default only SuperAdmins (in multisite) / admins (in single site) can create forms, however there is a settings allowing them to give lower roles… | ||
| CVE-2023-0272 | Med | 0.35 | 5.4 | 0.01 | Mar 27, 2023 | The NEX-Forms WordPress plugin before 8.3.3 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting… | ||
| CVE-2021-24705 | Med | 0.31 | 4.8 | 0.00 | Dec 13, 2021 | The NEX-Forms WordPress plugin before 8.4.3 does not have CSRF checks in place when editing a form, and does not escape some of its settings as well as form fields before outputting them in attributes. This could allow attackers to make a logged in admin edit arbitrary forms… |
- risk 0.61cvss 8.8epss 0.10
The NEX-Forms WordPress plugin before 7.9.7 does not properly sanitise and escape user input before using it in SQL statements, leading to SQL injections. The attack can be executed by anyone who is permitted to view the forms statistics chart, by default administrators, however…
- risk 0.50cvss 7.2epss 0.45
The NEX-Forms WordPress plugin before 8.4 does not properly escape the `table` parameter, which is populated with user input, before concatenating it to an SQL query.
- risk 0.49cvss 7.5epss 0.02
Basix NEX-Forms through 7.8.7 allows authentication bypass for Excel report generation.
- risk 0.49cvss 7.5epss 0.02
Basix NEX-Forms through 7.8.7 allows authentication bypass for stored PDF reports.
- risk 0.35cvss 5.4epss 0.00
Cross-Site Request Forgery (CSRF) vulnerability in Basix NEX-Forms – Ultimate Form Builder – Contact forms and much more.This issue affects NEX-Forms – Ultimate Form Builder – Contact forms and much more: from n/a through 8.5.2.
- risk 0.35cvss 5.4epss 0.00
The NEX-Forms WordPress plugin before 8.4.4 does not escape its form name, which could lead to Stored Cross-Site Scripting issues. By default only SuperAdmins (in multisite) / admins (in single site) can create forms, however there is a settings allowing them to give lower roles…
- risk 0.35cvss 5.4epss 0.01
The NEX-Forms WordPress plugin before 8.3.3 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting…
- risk 0.31cvss 4.8epss 0.00
The NEX-Forms WordPress plugin before 8.4.3 does not have CSRF checks in place when editing a form, and does not escape some of its settings as well as form fields before outputting them in attributes. This could allow attackers to make a logged in admin edit arbitrary forms…