mediumCVE-2026-1946

GW AI Website Builder <= 1.0.1 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Plugin Settings Deletion

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

GW AI Website Builder versions listed as affected should be reviewed: *-1.0.1.

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 GW AI Website Builder plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the gwaiwebu_gravitywrite_disconnect_handler() function in all versions up to, and including, 1.0.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to disconnect the plugin from GravityWrite via the 'gwaiwebu_gravitywrite_disconnect' AJAX action.

ProductGW AI Website Builder

CVSS4.3

EPSS0.00222

UpdatedJuly 13, 2026

Quick answer

GW AI Website Builder 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

*-1.0.1

Fixed versions

1.0.2

How to fix it

GW AI Website Builder is affected by CVE-2026-1946, a authorization bypass issue in versions up to 1.0.1. Wordfence lists the official remediation as updating to version 1.0.2, 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 GW AI Website Builder installed, including production, staging, multisite, client, WooCommerce, support, booking, and content-management environments.
Confirm the installed GW AI Website Builder version and compare it with the affected range from the Wordfence advisory.
Update GW AI Website Builder to version 1.0.2, or to a newer vendor-supported patched version from the official WordPress update channel.
If the update cannot be applied immediately, disable GW AI Website Builder 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 GW AI Website Builder version is version 1.0.2 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 Wordfence advisoryWordfence, NVD

FAQ

What is affected by CVE-2026-1946?

GW AI Website Builder versions listed as affected should be reviewed: *-1.0.1.

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.