mediumCVE-2026-9017

NEX-Forms <= 9.2.2 - Missing Authorization to Unauthenticated Arbitrary Form Entry Modification via nf_send_nf_email AJAX Action

Q: What is affected by CVE-2026-9017?

NEX-Forms – Ultimate Forms Plugin for WordPress versions listed as affected should be reviewed: *-9.2.2.

Q: What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

Q: How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

Q: How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.

The NEX-Forms – Ultimate Forms Plugin for WordPress plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 9.2.2. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to overwrite the saved_admin_email, saved_user_email, and saved_user_email_address fields of arbitrary form entries belonging to other users, and cause the site to dispatch attacker-controlled email content to attacker-chosen recipient addresses.

ProductNEX-Forms – Ultimate Forms Plugin for WordPress

CVSS5.3

EPSS0.00273

UpdatedJuly 13, 2026

Quick answer

NEX-Forms – Ultimate Forms Plugin for WordPress should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

*-9.2.2

Fixed versions

9.2.3

How to fix it

NEX-Forms – Ultimate Forms Plugin for WordPress is affected by CVE-2026-9017, a authorization bypass issue in versions up to 9.2.2. Wordfence lists the official remediation as updating to version 9.2.3, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, support, booking, import/export, page-builder, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or feature, restrict access, and monitor for exploitation until the update is installed.

Inventory every WordPress site that has NEX-Forms – Ultimate Forms Plugin for WordPress installed, including production, staging, multisite, client, WooCommerce, support, booking, and content-management environments.
Confirm the installed NEX-Forms – Ultimate Forms Plugin for WordPress version and compare it with the affected range from the Wordfence advisory.
Update NEX-Forms – Ultimate Forms Plugin for WordPress to version 9.2.3, or to a newer vendor-supported patched version from the official WordPress update channel.
If the update cannot be applied immediately, disable NEX-Forms – Ultimate Forms Plugin for WordPress or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
Review affected REST endpoints, AJAX actions, roles, capabilities, account changes, orders, bookings, payments, tickets, marketplace actions, and admin actions for unauthorized activity.
Rotate administrator sessions, API keys, webhook secrets, payment or integration tokens, and affected credentials if logs or content review suggest compromise.
Clear WordPress, object, CDN, page-builder, security plugin, WooCommerce, booking/support plugin, and browser caches after patching so vulnerable assets or stored payloads are not served.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

Confirm the running NEX-Forms – Ultimate Forms Plugin for WordPress version is version 9.2.3 or newer, and record the patched version in the remediation ticket.
Verify unauthenticated or low-privilege users can no longer trigger the affected action, endpoint, account, payment, booking, ticket, import/export, snippet, or settings change.
Review web server, WordPress, security plugin, WAF, database, WooCommerce, booking/support, and application logs for exploitation attempts before and after the fix.
Retest normal visitor, subscriber, customer, editor, administrator, checkout, form, API, booking, support ticket, import/export, backup/restore, snippet, or integration workflows to confirm expected behavior still works.
Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.

Related categories

WordPress Authorization Bypass

Trusted references

Wordfence advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Wordfence advisoryWordfence, NVD

FAQ

What is affected by CVE-2026-9017?

NEX-Forms – Ultimate Forms Plugin for WordPress versions listed as affected should be reviewed: *-9.2.2.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.