Checked as of 30 October 2026.

Three WordPress plugin advisories were published or updated on 29 October 2026. Each concerns a plugin that many small and medium business websites rely on for contact forms or chat. The reviewed notices do not establish attacks against your website. Treat them as disclosures to act on where they apply, not as a diagnosis or proof of compromise.

What was disclosed

Gravity Forms, CVE-2026-103039

Applies to: Gravity Forms 3.1.2 or earlier where a form uses a Post Custom Field of the List input type with a content template. The flaw is unauthenticated PHP object injection. Code execution still depends on further site-specific conditions, so not every form or site is equally exposed (Wordfence).

How to check: ask your provider to confirm the installed version and whether any live form uses that field configuration.

Action: update to 3.1.3 or a newer patched release. The vendor changelog shows the fix shipped before this disclosure date (Gravity Forms changelog).

Formidable Forms, CVE-2026-89435

Applies to: free Formidable Forms 6.35 or earlier without Formidable Pro, where a logged-in user holding the delegable frm_view_forms capability could install arbitrary plugins (Wordfence). Ordinary subscribers are not automatically in scope.

How to check: your provider reviews the installed version, whether Pro is present, and which roles hold that capability.

Action: update to 7.0 or a newer patched release. The vendor readme lists permission and download URL hardening in 7.0 (Formidable Forms readme).

AI Engine, CVE-2026-110732

Applies to: AI Engine 3.8.6 or earlier with the relevant MCP OAuth route exposed. An unknown client can register, but administrator-level control follows only after an administrator approves it on a consent screen, which clickjacking could disguise (Wordfence). Chatbot use without MCP is a different exposure.

How to check: your provider confirms the version, whether MCP is enabled, and which clients are connected. Administrators should reject any consent prompt they did not initiate.

Action: update to 3.8.7 or a newer patched release. The vendor readme notes anti-framing sign-in hardening in 3.8.7 (AI Engine readme).

Managing the updates as an owner

Patching is a small project, and the owner’s job is to make it boring. These are checks we suggest owners run, not steps every listed vendor requires.

  • Know what you run. Obtain a plugin inventory with versions and name one person responsible for applying patches and confirming the result.
  • Back up before touching anything. Database and files together, with a restore path that has actually been tested. Our guide to backup rules and restore testing covers what to ask for.
  • Stage, then move quickly. Test updates on a staging copy, but do not leave production unfixed for days while staging waits for attention.
  • Agree timing and fallback. Fix a window with your provider, decide what rollback looks like, and confirm who makes that call.
  • Validate the customer path. After updating, submit each public form with synthetic data and confirm receipt and notifications. Check quote, booking or checkout flows the same way, without live charges.
  • Record the outcome. Note the exact installed patched version, the date, which components changed, and anything still open.

If something already looks wrong

If your provider finds unfamiliar administrator users, unknown connected MCP clients or plugins nobody installed, preserve logs and evidence before changing anything. Ask a qualified provider to assess containment and recovery. A patch addresses the listed weakness. It does not remove access someone may already have gained, and it does not guarantee that every future attack is blocked.

Next step

If you want a second opinion on where these three plugins sit in your stack, we are happy to discuss a documented maintenance scope through our WordPress maintenance service.